I wondered if there is a standard way in locust to detect and warn about performance degradation between runs. E.g.
Suppose I have an endpoint GET /helloworld that returns a json like:
{"message":"hello world"}
on run1 of the performance test suite, the response time was 1 second, but running the locust command, now returns in 3 secs. In my contrived example, lets say 3 secs is an 'acceptable' response time, thus we don't want to fail the test. However, the performance of the endpoint has degraded and we want to warn about this. What is the best way to achieve this in locust?
I thought maybe to save the results in csv after each run and do a comparison with the csv produced by the current/last run, but is there an easier way to achieve this? Thanks!
