Test methodology overview
Apica ZebraTesterTM - https://www.apicasystem.com/load-testing/tools/
The purpose of this test is to quickly locate bottlenecks in the system and to determine the maximum throughput of the system. We let a relatively low number of users go through the test scenario as many times as possible during 5 minutes (default), with short idle times between each step in the user journey. We then double the number of users - expecting a corresponding increase in throughput – and continue like this until we reach the so called ”Performance knee”, where the throughput levels out and the response times and/or failure rate increases.
Sometimes referred to as “Load Testing” methodology.
The purpose of this test is to determine the maximum number of simultaneous users and connections in the system. We test with the actual number of active users, which means that the number of users is higher than in the stress tests, and we increase the idle time (and the total length of the user session) between each step in the scenario to simulate more realistic user behaviour.
Mixed concurrency testing
Same test methodology as “Concurrency test” only that multiple scenarios are run in parallel with a weighted amount of users.
Disaster recovery testing
The underlying test methodology to be used is the “Mixed concurrency” method. However, this test methodology aims to assess how the system behaves during disaster recovery situations. Such situations might be; restart during load, failover, recovery after overload outage etc.
This test method aims to see how the system scales according to the number of different environment instances. I.e. number of web servers, databases, application servers etc. The underlying test methodology used is the “Concurrency test” method
Sometimes referred to as “Soak testing” and/or “Stability testing”
Endurance test methods will assess the application- and systems performance stability under sustained load (normally 6-8 hours test duration). The underlying test methodology to be used is the “Concurrency test” method.
Volume testing refers to testing a software application with a certain amount of data (i.e. reading and/or writing on to/from a file of a certain size/volume).
Continuity testing refers to testing a systems availability to continue during periods of systems disruptions. Continuity testing sometimes refers to business continuity testing assessing the business ability to continue operations regardless of the state of the IT system.