The Test Process | QA Decoded

A structured test process turns ad-hoc checking into repeatable quality assurance

CTFL defines a clear sequence of activities that helps teams plan effort, track progress, and know when testing is complete enough to release.

// example: uber driver onboarding flow

Before launch, the team follows the test process: they analyze requirements to identify test conditions (e.g., document upload, background check status), design test cases for each condition, set up a staging environment with mock services, execute tests including edge cases like network loss during upload, log defects for any failures, and finally report coverage and residual risk to the release manager.

CTFL 4.0.1 Test Process Activities

Test Planning and Control — Define objectives, scope, approach, resources, and schedule. Monitor and adjust throughout.
Test Analysis and Design — Identify test conditions from requirements, design test cases, create test data, and define expected results.
Test Implementation and Execution — Build test suites, set up the test environment, execute tests, and log results and defects.
Evaluating Exit Criteria and Reporting — Assess whether testing objectives are met, summarise results, and report residual risk.
Test Closure Activities — Archive artefacts, document lessons learned, hand over testware, and evaluate the process for improvement.

These activities are iterative and may overlap, especially in agile contexts where testing occurs within each sprint.

// tip: Exam Tip: Remember the order: Plan → Analyze/Design → Implement/Execute → Evaluate/Report → Close. Questions often shuffle these to test your understanding.

Process Activity	Concrete Actions for Password Reset
Planning	Define scope: test email link expiry, token reuse, rate limiting. Allocate 3 days, 1 tester.
Analysis	Identify conditions: valid email, invalid email, expired token, already-used token, brute-force attempts.
Design	Write test cases: TC01 valid reset, TC02 expired link, TC03 token replay, with expected results.
Implementation	Prepare test data (test emails), configure mock email service, set up test accounts.
Execution	Run TC01-TC03, log defect if expired token is accepted, re-test after fix.
Evaluation	Check: all high-priority cases passed? Defects resolved? Report: 95% coverage, low residual risk.
Closure	Save test cases to repository, document that rate-limiting needs monitoring in production.

Plan & Control

Define scope, approach, resources, schedule

// CTFL 4.0.1 note

Activities are iterative and may overlap in agile contexts.

Aspect	Waterfall Context	Agile Context
Planning	Upfront, detailed test plan document	Lightweight, just-in-time planning per sprint
Analysis/Design	Based on complete requirements	Based on user stories, continuous refinement
Execution	Large batch after development phase	Continuous, alongside development
Reporting	Formal milestone reports	Daily stand-ups, sprint reviews
Closure	End-of-project sign-off	Retrospectives, continuous improvement

// warning: Exam Trap: "Test execution" is NOT the first step. Many candidates forget planning and analysis. The process starts with planning, even in agile.

Exam Practice Questions

// ctfl 4.0.1 style — select an answer to reveal explanation

Q1.Which activity belongs to the "Test Analysis and Design" phase of the test process?

Q2.When should exit criteria be evaluated in the test process?

Q3.Which of the following is a test closure activity?