Software Testing: Fundamental Test Process
- Get link
- X
- Other Apps
Fundamental
Test Process.
Planning and analysing are very necessary activities that amplify the benefits of execution.
Although in broad sequence, they are not rigid.
A defect found in test execution can sometimes be resolved by adding functionality that was originally not present. The new features themselves have to be tested, so the 'earlier' activity of analysis and design has to be performed.
We sometimes need to do two or more of the main activities in parallel. Time pressure can mean that we begin test execution before all tests have been designed.
Overlapping phases.
Planning feeds into control. Analysis bridges planning and execution. Execution loops back to analysis when new features emerge. The process is alive.
Planning
& Control.
Determining what is going to be tested and how. Drawing the map, defining who will do what, and setting test completion criteria. Control is comparing progress against the plan — monitoring to measure, control to adjust.
Analysis
& Design.
The bridge between planning and execution. Looking backward to schedules and forward to expected results. Reviewing the test basis, identifying test conditions, designing tests with priority, and detailing the test environment and data required.
Not just running tests — but combining, logging, comparing, and investigating.
Test implementation and execution involves running tests, including any set-up and tear-down activities. The most important tests need to be run first — determined during planning and refined during design.
One important aspect is combining test cases into an overall run procedure, so that the outcome of one test creates the preconditions for later tests.
Has the
problem
been fixed?
Looking in fine detail at the changed area of functionality. Re-executing a previously failed test to confirm that the fix is effective.
Has anything
else
broken?
Covering all the main functions to ensure that no unintended changes have occurred. On a financial system, include end of day/month/year processing.
Evaluating exit
criteria & reporting.
Exit criteria were defined during planning. At the end of execution, check if they have been met. If the target was 85% statement coverage and the result is 75%, there are two options: change the exit criteria, or run more tests. Write a test summary for stakeholders.
Test closure
activities.
Making sure everything is tidied away. Documentation in order, incidents closed, deferred defects clearly marked. Archiving the test environment and passing testware to the maintenance team. Writing down lessons learned to improve testing maturity.
Five stages. One process.
- Get link
- X
- Other Apps