Performance Testing is big! Mind-boggling big especially for software testers charged with completing it. And it is not going to get smaller with the Internet-of-Things coming at Warp Speed.
In effort to subdivide and conquer the need for Performance Testing we are going to define some sub-divisions and then discuss them in detail in the next few weeks. Here they are:
Volume Testing Volume testing confirms that any values that may become large over time (such as accumulated counts, logs, and data files) can be accommodated by the program and will not cause the program to stop working or degrade its operation in any manner.
Risk if not completed – It may not be possible to operate the complete system with all data in place if the volume of expected records is not checked during testing and verified to work correctly and completely.
Stress Testing Stress testing confirms that the program continues to operate when subjected to stress (that is, during a short, sharp peak of intensive activity).
Risk if not completed – Users may find the system response becomes non-existent or unacceptably slow under some conditions if the system is not confirmed to operate properly under conditions of stress.
Load Testing Load testing confirms that the program operates without memory loss or degradation of performance for several days without being shut down
Risk if not completed – The client may find that when they place the system under load to complete a number of transactions on an ongoing basis the system will not respond appropriately.
Speed-of-Response Testing Speed-of-Response testing checks the program’s speed. It checks both speed of response to the user and speed of execution of any underlying batch programs, under conditions of both normal and stress usage.
Risk if not completed – The client may find the system is too slow to meet the user needs.
Storage Testing Storage Testing checks that the program stores data files in the correct directories and that it reserves sufficient space to prevent unexpected termination resulting from lack of space. Storage of historical data is also considered here.
Risk if not completed – The client may find that the system cannot store the expected volume of records and this may cause unexpected and unknown errors.
- How do you define Performance Testing?
- Was the Performance Testing successfully completed?
- Were other items discovered later?
Next Week: Why Quality Assurance Management