Please enable JavaScript.
Coggle requires JavaScript to display documents.
Testing Strategies and Techniques (Test Analysis and Design (Review the…
Testing Strategies and Techniques
Terminology
Error
A human action that produces an incorrect result
Defect
A flaw in a system that can cause it to fail to perform its required function
Failure
Deviation of a system from its expected delivery, service or result
May be caused by data, hardware or environmental conditions
How much software testing is enough?
As testing progresses the number and severity of defects found will typically trail off
The same amount of effort later in the project is likely to find fewer defects than early in the project
Test Planning and Control
Planning
Determine the scope and risks
Implement test policy and strategy
Determine the test approach
Determine the rquired test resources
Schedule the test activities
Determine entry and exit criteria
Control
Monitor testing activities and results
Compare actual progress and test coverage against plan
Take corrective actions as required
Test Analysis and Design
Review the test basis
Evaluate the test basis for testability
Identify and prioritise test conditions
Design and prioritise high-level test cases
Identify test data to support test conditions and test cases
Design the test environment set-up
Create bi-directional traceability between the test basis and test cases
Test Implementation and Execution
Implementation
Finalise, implement and prioritise test cases
Develop and prioritise test procedures
Create test suites from the test procedures
Create test data
Verify the test environment has been set up correctly
Execution
Execute test procedures according to the planned sequence
Log the outcome of test execution
Compare actual results with expected results
Re-test and regression test as required
Evaluating Exit Criteria and Reporting
Check test logs against the exit criteria
Assess if more tests are needed or if the exit criteria should be changed
Write a test summary report for stakeholders
Test Closure Activities
Check planned deliverables have been produced
Close incident reports
Document thee acceptance of the system
Finalise and archive testware and the test environment
Hand over to maintenance
Analyse lessons learned