Test design is a process that describes “how” testing should be done. It includes processes for the identifying test cases by enumerating steps of the defined test conditions. The testing techniques defined in test strategy or plan is used for enumerating the steps.

The test cases may be linked to the test conditions and project objectives directly or indirectly depending upon the methods used for test monitoring, control and traceability.

The objectives consist of test objectives, strategic objectives and stakeholder definition of success.

When to create test design?

After the test conditions are defined and sufficient information is available to create the test cases of high or low level, test design for a specified level can be created.

For lower level testing, test analysis and design are combined activity. For higher level testing, test analysis is performed first, followed by test design.

There are some activities that routinely take place when the test is implemented. These activities may also be incorporated into the design process when the tests are created in an iterative manner.

An example of such a case is creation of test data.

Test data will definitely be created during the test implementation. So it is better to incorporate it in the test design itself.

This approach enables optimization of test condition scope by creating low or high level test cases automatically.

You can also go through Test Design as it was explained for the foundation level.

In the next article we will learn what is test implementation.

Other popular articles:

• What are Test Conditions & Test Analysis? Advantages, Disadvantages & Level of Detail
• What is fundamental test process in software testing?
• What is Test analysis / Test Basis? or How to identify the test conditions?
• What is Test Execution?
• What is a Test Case? Example Template, Types, Best Practices