In ISTQB glossaire “Test Process” is defined as :
The fundamental test process in the Software Test Cycle:
* Test planning and control
* Test analysis and design
* Test implementation and execution
* Evaluating exit criteria and reporting
* And test closure activities.
ISTQB Glossary : Search term = test process
The second process is called as “Test analysis and design” right after “Test planning and control” where requirements and specifications are analysed and test cases designed. The ISTQB Test process has this formal phase introduced to insist on fore-thought and planning, and hence avoiding re-work and to get it right the first time.
In this test phase, specifications are analysed to understand what the application’s functions are – the screens, the actions, database updates, error messages, flow of data/info etc. The specifications are analysed to check how clear and complete the information is, for any confusion, ambiguities(unclear), for any discrepancies(conflicting actions), and more importantly how to test and verify the function in the system. The reviews and clarifications done early in this stage helps build a greater understanding of the product and hence an improvement to cost, quality and time in later stages.
Test Analysis is needed to evaluate the test basis for testability!
ISTQB mentions a 3-step process to the test design process – Test Conditions, Test Cases, Test Procedures.
- Test Conditions: a test condition verifies a small section of the Functional Specification. eg. Registration, Login etc
- Test Cases: pre-conditions, a set of inputs, expected outcome and the post-conditions to verify the Test Condition
- Test Procedure : actual sequence of actions or steps to execute the test
