Software Testing: Your Most Frequently Asked Questions Answered
We are also always on hand to assist with any questions you might have when it comes to software testing. The following are some of the most frequently asked questions we get when we start working with our clients.
What is Performance Testing?
Software performance testing is a non-functional testing activity (link to what is functional and non-functional testing FAQ) and is a way of validating that software meets the performance specification as documented in the requirements. Performance metrics are provided, and a tester will generate test cases with the aim of measuring the system performance under different scenarios.
Normally, performance testing includes:-
- Load Testing
- SOAK / Endurance Testing
- Stress Testing
The aim of load testing is to see how a system or component handles increased activity, such as transactions or parallel users. For established businesses, assessing existing traffic or user loads can provide some metrics to work with.
SOAK or endurance testing is essentially running the load test, over a defined period of time. This tests that your solution can handle increased workload for a prolonged period. For example, if you anticipate increased traffic on your website over specific periods of the year.
Stress Testing is carried out to learn more about the break point of a system or component. If a system regularly gets 1,000 parallel users in an hour, a stress test would continue to load more parallel users until the system started to report failures. If the system starts to fail at 1,100 parallel users, there may be more infrastructure, software or hardware changes you can make to increase the number of users the solution can handle. If, however, the breakpoint is 15,000, you can help the business understand whether there are likely going to be issues with this, once the solution is released to the end users.
In addition to these standard areas, more targeted performance testing can be conducted with a closer knowledge and understanding of how the system is used. Examples of this targeted performance testing can include:
- User interactions – targeting the measuring the performance impact of certain users performing specific actions at the same time (such as checking out on an eCommerce store). This can be used to specifically test potential bottlenecks/weak points of the system.
- Business User Interactions – this involves performance testing the system while key back office BAU tasks are taking place – such as batch jobs, data loads etc. to assess if there is an impact to front end users of the system.
If you want to deliver world class software testing and enhance the profitability of your business, get in touch with us today.
+44 (0)114 399 2820