-
Notifications
You must be signed in to change notification settings - Fork 209
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Capture timing of requests #1153
Labels
Comments
As a starting point, we can record the latency as fixed delay in capture mode. It seems easy to implement. |
@tommysitu can I pick this up? |
@kapishmalik of course if you have time. Thank you! |
Sure, I will manage and start working on the same. |
Raised PR - #1154 |
Very cool to see the quick turnaround on this idea! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
(I'm new to Hoverfly)
Is your feature request related to a problem? Please describe.
I think Hoverfly could be useful not just for unit testing, but performance testing.
In (some forms of) performance testing, I would like to stub out my application's connections to downstream webservices and return fixed responses, but with realistic (data-driven) delay.
Describe the solution you'd like
Could
Capture
mode be enhanced to grab not only request/response, but also the time taken for the roundtrip? This data could (minimally) be read by the developer to better-inform "hardcoded" delays, or a step further, could feed directly intoSimulate
mode.Describe alternatives you've considered
Manually researching and configuring delays for requests.
The text was updated successfully, but these errors were encountered: