Premium Load and Performace Testing with NeoLoad

We like to
have easy-to-maintain test cases. That’s why we shifted load and performance
tests from JMeter to Neoload. Currently, we are testing web applications automated. SAP is in the queue.
But there are several learnings: In preparing the tests, we need
a storybook or a TOSCA automated end-to-end test case to minimize the effort
during scripting. This also contains login information and test data. No try
and error during scripting!

The execution phase is an online meeting that acts as a war room where all
necessary stakeholders are invited. They are responsible for monitoring the
systems and collecting traces. In the analysis phase, all collected
information is consolidated into a report. The results are discussed in the result meeting. Here we decide on measures and next steps. We learned that load
testing is a team sport.

We use NeoLoad, Neoload Web, Jira, Xray, and Jenkins. NeoLoad is used for performance testing, and NeoLoad Web shows the results in the intranet. We are not only running manual performance tests. We have also implemented automated performance tests using Jenkins. The results of the automated performance tests are replicated in Jira and Xray. Each team member of the development teams and test team has access to the tools Jira and Neoload Web.

At the beginning of performance testing in our organization, we used Jmeter with high efforts of script maintenance. With NeoLoad, we increased the test coverage from 10% to 90% with 7 times greater system coverage. In addition, we implemented load and performance tests with NeoLoad, which are triggered automatically by Jenkins. They are executed as regression daily.