5 exercises — practise writing professional scope sections, entry/exit criteria, objectives, risk entries, and suspension criteria in English.
0 / 10 completed
1 / 10
A QA lead is writing the Scope section of a test plan for a new checkout module. Which statement best represents how the "out of scope" sub-section should be written?
Out-of-scope items must be explicitly named and explained.
Options A and D are too vague and incomplete. Option B is conversational — "we won't test everything" is ambiguous and unprofessional. Option C uses the standard structure: a clear list of excluded areas with a note about where they will be addressed, preventing scope ambiguity and managing stakeholder expectations.
Key vocabulary:
• Out of scope — formally excluded from the current test effort; must be explicitly listed
• Scope creep — uncontrolled expansion of testing beyond agreed boundaries
• Dedicated test plan — a separate document for a specific testing concern (performance, security)
• Stakeholder expectations — the assumptions of those who authorized and will review the testing effort
2 / 10
Your team is defining entry criteria for a testing phase. Which of the following most accurately represents a professional entry criterion statement?
Entry criteria must be measurable, specific, and objectively verifiable.
Options A and D rely on informal communication — "developers say they are done" or "QA receives a notification" can mean different things to different people. Option B lacks verifiability beyond a commit event. Option C specifies three observable conditions: feature merge, deployment confirmation, and smoke test pass — each verifiable by any team member independently.
Key vocabulary:
• Entry criteria — conditions that must be met before testing can begin
• Exit criteria — conditions that must be met before testing is considered complete
• Smoke test — a shallow set of tests confirming basic functionality works after a new build
• Staging environment — the pre-production environment used for integration and acceptance testing
3 / 10
A QA engineer needs to write the Objective section of a test plan for a payment integration. Which option most professionally expresses the test objective?
Test objectives must be specific, measurable, and tied to documented requirements.
Options A and B use imprecise language: "works properly" and "test all features" are not measurable outcomes. Option C is more professional but centers on defect discovery rather than verification against requirements. Option D references the specific PRD, names exact flows under test, and distinguishes standard from edge-case conditions — giving every reader a clear definition of success.
Key vocabulary:
• Test objective — the stated purpose and expected outcome of a testing effort
• Functional requirements — documented specifications of what the system must do
• Edge case — an unusual or boundary input that may reveal system weaknesses
• Authorisation / capture / refund — key stages in a payment transaction lifecycle
• PRD (Product Requirements Document) — the source-of-truth specification for a feature
4 / 10
A QA lead is writing the Risk section of a test plan. The team depends on a third-party payment gateway that may be unavailable during testing. Which formulation is the most professional?
Risk entries must include likelihood, impact, and a concrete mitigation strategy.
Options A and B identify the risk but provide no structure or plan. Option D proposes rescheduling, which avoids the risk rather than mitigating it. Option C follows the professional risk-register format: a named risk, estimated likelihood and impact, and a specific mitigation (mock service plus separately tagged real-gateway tests), giving the team a clear path forward regardless of gateway availability.
Key vocabulary:
• Likelihood — the estimated probability that a risk will materialise
• Impact — the severity of consequences if the risk occurs
• Mitigation — a planned action to reduce the probability or impact of a risk
• Mock service — a simulated external dependency used to isolate system testing
• Sandbox environment — a third-party test environment provided for integration testing
5 / 10
A test plan should include suspension and resumption criteria. The staging environment has gone completely offline mid-sprint. Which statement best describes a professional suspension criterion?
Suspension and resumption criteria must specify measurable thresholds and clear restoration conditions.
Option A describes a defect management concern, not an environmental suspension trigger. Option B is too broad — "any instability" could mean a 30-second blip. Option C describes a workflow practice, not a formal suspension criterion. Option D gives a specific time threshold (4 hours), defines the technical check required to resume (smoke suite pass), and specifies a communication step (build confirmation), making the criteria unambiguous and actionable.
Key vocabulary:
• Suspension criteria — the conditions under which testing is formally paused
• Resumption criteria — the conditions that must be met before paused testing can restart
• Smoke test suite — a set of high-level tests confirming basic system health after a deployment
• Build confirmation — notification from the CI/CD pipeline confirming a stable, deployable build
6 / 10
Sarah, a QA engineer, is drafting the 'Test Environment' section of a test plan for a new mobile app. The team has configured a dedicated staging environment mirroring production but with anonymized user data. Which of the following best describes how to document this setup for clarity and reproducibility?
The key here is providing enough detail for another developer to recreate the setup. Option 1 describes the infrastructure without focusing on its purpose – mimicking production. Option 2 highlights the crucial element of anonymized data, which is vital for testing sensitive user information. Options 3 and 4 are too technical and don't convey the core function of the staging environment.
7 / 10
During a code review for a new feature that handles user profile updates, David, the reviewer, notices a comment from Mark, the developer: 'I've added error handling to deal with null values.' David should respond with which of the following statements?
David needs to encourage further clarification. While logging is good practice, Mark's initial comment lacks detail. Option 2 prompts for specifics about error handling – what messages are logged, and how will they be addressed? Options 3 and 4 offer simplistic or technically incorrect solutions.
8 / 10
As a QA lead preparing a test plan for an API endpoint responsible for processing image uploads, you need to define a success criteria. Which of the following is the most professional and measurable approach?
Success criteria must be clearly defined and objectively verifiable. A 200 OK status code is a standard HTTP response indicating successful reception of data. While checking for image presence in the database could be part of subsequent validation, it's not a direct measure of the upload *process* itself. Option 4 focuses on performance which isn't a criterion.
9 / 10
During a daily standup meeting, Emily (a QA engineer) reports: 'I'm blocked because the automated tests are failing intermittently.' Which of the following statements best reflects her professional communication to the team?
Emily's statement clearly and concisely describes the problem and requests assistance. It avoids overly emotional language (Option 1) or assigning blame (Options 3 & 4). Option 2 is more proactive by stating she needs help. A standup update should be focused on impact and needing support, not a detailed technical description.
10 / 10
The development team is testing a new feature that integrates with a third-party payment processor. The processor occasionally experiences downtime. What's the most appropriate statement to include in the test plan regarding this potential issue?
Acknowledging potential external dependency failures is critical for realistic testing. Option 1 is dangerously naive. Option 2 correctly identifies a crucial test scenario – simulating failure. Options 3 and 4 demonstrate a lack of awareness regarding the inherent risks associated with third-party integrations.
This exercise, "Test Plan Writing", tests your understanding of testing & qa lab vocabulary and phrasing through 10 multiple-choice questions drawn from real workplace scenarios.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 10 questions. Each one presents a realistic sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Who is this Testing & QA Lab exercise for?
It's designed for IT professionals and learners who want to sound natural discussing testing & qa lab topics in English — useful for meetings, documentation, interviews, and day-to-day communication with English-speaking teams.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more Testing & QA Lab exercises?
Browse the full Testing & QA Lab exercises hub for more practice, or explore other exercise categories covering vocabulary, grammar, interviews, and workplace communication.