-
Test Planning
-
Test Analysis and Specification
-
Test Execution
-
Test Recording (Verification)
-
Checking for Completion.
Test Planning: The Test Plan describe how the Test Strategy is implemented.
Involves producing a document that described an overall approach and include test objectives.
Contents of a Test Plan Includes:
1. Background 2. Reference documents 3. Approach 4. Method
5. Timetable 6. Resources 7. Dependencies
8. Report 9. Test Asset Identification 10. Exit Criteria
- The most critical stage of the process
- Effort spent now will be rewarded later
- The foundation on which testing is built
Test Specification (Sometimes referred to as test design)
- Preparation & analysis
- Building or design test conditions and test cases using recognized test techniques
- Define expected results
Test preparation: Analyse the Application, Identify good test conditions, Identify tes cases, Document thoroughly and cross refercing among the team.
Building Test Cases: Test cases comparise of standard data, transaction data, actions and expected results
- The outcome of each action
- The state of the application during test and after test
- the state of the data during test phase and after the test phase
Test Execution
- Test execution schedule / log
- Identify which tests are to be run
- Test environment primed & ready
- Resources ready, willing & able
- Back-up & recovery procedures in place
- Batch runs planned and scheduled
If all this are in place then we are ready to run carry out our tests
Test Recording: involves keeping good records of the test activities that you have carried out.
For example , version of the software you have tested and the test specifications are recorded, along with the actual outcomes of each test.
Test verification:
- If our planning and preparation is sufficiently detailed this is the easy part of software testing
- The test is run to verify the application under test
- The test itself either passes or fails!
The test log should record:
- Software and test version control
- Specifications used as test base
- Test timings
- Test result ( Actual results and Expected results)
- Defect details for erroneous tests
Test Completion
Test Exit Criteria
Used to determine when to implement the software
- Budget used
- Defect detection rate
- Performance satisfactory
- Test Coverage
- Key Functionality tested