1.5 Test Process, Testware, and Traceability
Key Takeaways
- The test process includes planning, monitoring, analysis, design, implementation, execution, completion, and control activities.
- Testware is the set of work products created or used for testing, such as test cases, data, procedures, environments, and reports.
- Traceability links test basis items, test conditions, test cases, defects, results, and requirements.
- Good traceability supports impact analysis, coverage assessment, reporting, and audits.
- The CTFL exam may describe activities out of order, so identify their purpose rather than relying only on sequence.
Process Activities
The CTFL test process is a set of related activities, not a rigid waterfall checklist. The activities include test planning, test monitoring and control, test analysis, test design, test implementation, test execution, and test completion. In iterative projects, these activities may overlap and repeat.
Test planning defines objectives, scope, approach, resources, schedule, risks, entry criteria, exit criteria, and deliverables. Monitoring compares actual progress with the plan. Control uses monitoring information to adjust the work, such as changing priorities when a high-risk defect appears.
Test analysis asks what to test. The tester studies the test basis, such as requirements, user stories, architecture, risk analysis, or regulations, and identifies test conditions. Test design asks how to test those conditions by deriving test cases, data needs, and expected results.
| Activity | Main output or focus |
|---|---|
| Analysis | Test conditions based on the test basis |
| Design | Test cases and coverage approach |
| Implementation | Test procedures, test suites, data, and environment readiness |
| Execution | Test results, logs, incidents, and defect reports |
| Completion | Summary reports, archived testware, lessons learned |
Test implementation prepares the testware needed to run tests. This may include scripts, suites, data files, environment configuration, stubs, drivers, automated checks, and manual procedures. Test execution runs the tests, compares actual and expected results, records outcomes, and reports defects when needed.
Testware is the collective name for testing work products. It includes plans, charters, conditions, cases, procedures, data, expected results, automated scripts, environment descriptions, defect reports, logs, metrics, and completion reports. Good testware makes testing understandable to people beyond the person who first created it.
Traceability is the ability to link related items. A requirement may trace to a test condition, which traces to test cases, results, and defects. A defect may trace back to a user story and forward to confirmation tests. Traceability helps answer questions such as which requirements have been tested, which high-risk areas lack coverage, and what tests must be rerun after a change.
CTFL questions often mix process terms. If the question says identifying what to test from a requirement, think analysis. If it says deriving test cases and expected outcomes, think design. If it says organizing tests into suites or preparing data, think implementation. If it says running tests and logging outcomes, think execution.
Completion matters too. A project should not just stop testing and lose the evidence. Test completion activities gather results, check whether completion criteria were met, archive useful testware, document unresolved risks, and capture lessons learned for future work.
A tester studies requirements and identifies test conditions to cover. Which test process activity is this?
Which items are examples of testware?
Select all that apply