Tag Info

Hot answers tagged

6

To know how to write a test plan one must first learn to plan a test. Planning test is a real thinker task. You should be asking a hell lot of question to learn about the domain of the project. You should learn about the stakeholders of the project. One part of planning consists of test estimation. Here is something that might get you started with it - ...


2

Let me give some advice I got from James Bach. He likes to make the distinction between a test plan and the test plan document. A test plan document is the written form of the test plan. This can vary quite a bit depending on the company you work for and in my experience can range from lean or minimal to bloated (I’ve seen so many bloated test plan ...


2

I agree with milinpatel17' above answer about Test Plan. Test Plan is a detailed layout and strategy to test a product or application. Before you start writing a test plan, consider these points first: Why to test -- objective What to test -- scope How to achieve objective -- required time and money (with number of resources) What approach -- Automation, ...


1

The usual definition of a test plan is detailed here. The image you've posted, however, is exactly how Microsoft Test Manager is organized. You create a "test plan" (in their terminology this means the tests to be executed) for a certain release or sprint. In a test plan, you may have one or more test suites, which contain test cases. (Normally grouped in a ...


1

This kind of depends on what the structure of your project actually is. So far your tests all seem concerned with the operation of the system as a whole, i.e. You appear to be doing only black box testing. If you want to test the units independently then you know need to open up the system and look inside it (white box testing). In this case you have ...



Only top voted, non community-wiki answers of a minimum length are eligible