Initial state testing is related to the checking of the software product performance. If this type of QC is performed properly, then one may discover up to 85% of performance problems with its help.
The economy of time is the main advantage of initial state testing. The point is performance testing is a rather complex process which requires the specified time for creating and launching the necessary tests.
Checking the system performance should include at least load tests and tests for checking the initial state of the system. Also, it is preferable to execute stress tests, checking the duration of system activity, and volume testing. It is important to separate each of the mentioned testing types.
What are the peculiarities of different performance checking types?
- Initial state testing – performed for each script with the different number of users, in order to define the baseline of the main reaction time.
- Load checking – performance testing under load with a different number of users.
- Stress testing – for defining the breakpoint of the system operation because of high load – boundary value.
- Volume testing – system checking with the certain amount of data.
Ideally, the tests for initial state checking should be conducted with 1,2,5,10,20, and 50 users for each script. Running such tests may take 20-30 minutes in order to gain average performance. The initial state tests create a clear vision of the system performance and help to save much time for identification and isolating the problems’ reasons.