You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
A huge part of performance testing is knowing "did something get slower" or "did something get faster", DLT doesn't provide a quick and easy way to see this with the exception of the summary results header.
Describe the feature you'd like
In a given test, allow the ability to set one of the runs as the "baseline"
Then, when viewing the detailed events of other runs within the same test, provide difference from baseline information.
Additional context
Blazemeter does this very well if you want ideas of what I'm talking about. I realize taking this too far may be a ton of work, but I think a scaled down version of what BlazeMeter does would be hugely beneficial for heavy users like myself.
If you'd like me to get into more details of what a "scaled down" version of this might look like, would be happy to work on requirements.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
A huge part of performance testing is knowing "did something get slower" or "did something get faster", DLT doesn't provide a quick and easy way to see this with the exception of the summary results header.
Describe the feature you'd like
In a given test, allow the ability to set one of the runs as the "baseline"
Then, when viewing the detailed events of other runs within the same test, provide difference from baseline information.
Additional context
Blazemeter does this very well if you want ideas of what I'm talking about. I realize taking this too far may be a ton of work, but I think a scaled down version of what BlazeMeter does would be hugely beneficial for heavy users like myself.
If you'd like me to get into more details of what a "scaled down" version of this might look like, would be happy to work on requirements.
The text was updated successfully, but these errors were encountered: