Here is the third part of my blog which I have written on testing. What to test? • What are the major features of the Application Under Test (AUT)? • What are your testing priorities, based on risk analysis? What is the relative importance of each element of the software functionality? • What are your overall quality goals (usability, functionality, reliability, performance, etc.)? How to test? • Which testing techniques will be used? You can find information about testing techniques in many testing books. Here are some examples: System tests to test the system as a whole across functional areas. Stress tests to test how the software reacts under repeated execution of the same operations. Installation to test that the system can be installed smoothly Security to test access to the system without authorization Boundary tests to exercise code at the data and system boundaries. Performance and load tests to test the performance of the system under load conditions. • How will defects/bugs be handled (severity classification, authorization to open/close bugs)? Who/When? • What are the resources needed (human resources, hardware)? • When will the various tasks be completed? To be continued…