Testing techniques mind map

Testing techniques mind map

1. Test Harnesses

   • To streamline software development and possibly to assist with future maintenance, some organisations use test harnesses to automate the testing processes. A test harness consists of predefined software and testing scripts, plus expected test results. The test harness can then be operated whenever a change is made to the software, enabling the developers to establish quickly whether or not changes been successful. The use of test harnesses can avoid the need to perform lengthy and time- consuming manual testing.

2. Performance testing

   • This is testing that is performed to determine how fast some aspect of the system performs under a particular workload. This can help demonstrate that a system meets performance criteria, it can compare two systems to find which performs better or it can measure what parts of the system are causing it to perform badly.

3. Volume testing and scalability testing

   • This is testing using the anticipated peak volumes of data input or network traffic and is necessary to test the performance (as opposed to the functionality) of a system under live conditions. Also, databases and log files are likely to increase significantly in size over time; and continued operation with these increased volumes needs to be tested. Some systems are used intensively at certain times of the year and volumes may increase dramatically at those times. Appropriate volume testing should be undertaken to ensure that organisations are not let down by inadequate processing or storage capacity. Students should consider appropriate examples of inadequate volume testing. For instance, the on-line tax return system has in the past been unable to cope with the increased volume of transactions immediately prior to the submission deadline, which then had to be extended.

4. Usability testing

   • This testing is a means for measuring how well people can use an ICT system or part of a system for its intended purpose. If usability testing uncovers difficulties, such as people having difficulty understanding instructions, knowing what to do next, interpreting feedback etc then developers should improve the design and re-test.

5. Multi-platform/portability testing

   • Some systems will be used on a range of different hardware and operating system platforms. Whilst theoretically the systems should operate identically, testing is needed on all the possible hardware/software platforms anticipated before live implementation.