Category Direction - Load Testing

Load Testing

Load testing is a common and typically important stage in the CI process for organizations of all sizes. We will help developers shift left by making performance decisions earlier in the development process by providing a measure of how software responds under load as changes are introduced.

Interested in joining the conversation for this category? Please join us in our public epic where we discuss this topic and can answer any questions you may have. Your contributions are more than welcome.

This page is maintained by the Product Manager for Testing, James Heimbuck (E-mail)

What's Next & Why

Now that the Load Testing MVC has been delivered we will focus on broadening adoption of the tool by adding it to AutoDevOps. We think this will allow more users to make use of the Load Testing feature, contribute feedback and ultimately make this better.

Maturity Plan

This category is currently at the "Minimal" maturity level, and our next maturity target is "Viable" (see our definitions of maturity levels). Key deliverables to achieve this are:

We may find in research that only some of these issues are needed to move the vision for this category forward. The work to move the vision is captured and being tracked in this epic.

Competitive Landscape

Azure DevOps

Azure DevOps offers in-product load testing. This consists of different types of tests including:

For URL type tests, the output contains information about the average response time, user load, requests per second, failed requests and errors (if any).

Travis CI/CircleCI

While, just as one could orchestrate any number of performance testing tools with GitLab CI today, Travis or CircleCI could be used to orchestrate performance testing tools, it does not have any built-in capabilities around this.

Top Customer Success/Sales Issue(s)

TBD

Top Customer Issue(s)

The most popular issue in this category is to Improve the metrics reports frontend. The current interface for Metrics Reports is especially hard to read when the number of metrics grows beyond 10 to 12 and we hope this solves that problem.

Top Internal Customer Issue(s)

The top internal customer request is to integrate the Load Performance Testing template into AutoDevOps. We are looking forward to getting additional feedback from internal customers as usage within the company expands.

Top Vision Item(s)

Our long term vision for Load Performance Testing is that customers trust their app is well tested to perform under load based on their real traffic trends and can see how performance is changing over time. Graphing Load tests over time and auto scaling load tests) will also move our vision for load testing forward.