Archive and graph load test results
Problem to solve
GitLab provides data from automated tests ran in pipelines to allow contributors to release quality changes quicker. Having load testing results / comparisons in each MR provides value in the context of a single change but does not allow Sasha or Delaney to see how performance of a service under load is changing over time for the better or worse.
- The same feature is provided by the jmeter performance plugin (https://www.jenkins.io/doc/book/using/using-jmeter-with-jenkins/)
- This is a sample report generated by the jmeter performance plugin
For Delaney, when a project's performance under load has changed over time, they want to have data to show this change is acceptable/bad and the rate of change so they can make an informed decision about performance changes vs features.
For Parker, when a feature's performance/usage/outcomes from users has changed, they want to have data from load tests showing the direction and rate of change, so they can make an informed decision about performance changes vs. features to develop.
- Some customers require proof that a service will perform under high load