ISTQB Study Centre

How to write a System Test Plan? Imagine for a moment you've just finished a web application for a client. Swimming around within that application is 100 bugs. What proportion of those bugs would you say is acceptable for the client to find (e.g. 50, 30, 10)? The point is, those bugs are going to be found by someone, and its either going to be you or the client. You can think of it as a sliding scale, the more bugs the client finds, the more your creditability suffers and the more damage you do to the business relationship. In the martial arts there's a saying; "expect the best, but prepare for the worst". The US Navy Seals have a slightly more gun-ho version which goes; "The more you sweat in training, the less you bleed in battle." Notice how it says the ‘ less ' you bleed in battle, implying that if you enter into combat, you are going to get bloody. Software development is like this too, if you're going to create software, you are going to ...

What Is a Test Plan? A test plan refers to a document that describes the scope, resource, schedule and approach of the projected testing activities. The test plan identifies the test items, features that need to be tester, the tasks that need to be carried out, the designated person who would perform each of these tasks as well as any risks that may be require contingency planning. In terms of software testing, test plans provide detailed information about the forthcoming testing efforts. These include: The scope of testing Test Schedule Test Deliverables Contingencies and Risks Release Criteria Test plan can also be considered to be the detailed document describing how the process of testing would proceed , who would perform the testing, what are the things that would be tested, how much time it would require to complete the testing process and the quality level to which the testing would be performed. Due to its importance, it is a frequently asked testing interview...