QA & Testing Phrases: Reporting Bugs and Quality Issues
5 exercises on professional QA and bug-reporting phrases. Choose the most natural and professional option.
0 / 10 completed
1 / 10
Which phrase is the most professional way to say you were unable to replicate a reported bug?
I couldn't reproduce this on my machine: This is the standard QA phrase for reporting that a defect was not observed in your environment. It is factual, neutral, and professional — it doesn't dismiss the reporter or blame their setup. Option A is too informal. Option B is dismissive and sounds defensive. Option D is unprofessional as it implicitly blames the reporter. In real testing conversations, this phrase opens a collaborative investigation: you would follow up by asking for steps to reproduce, environment details, and logs.
2 / 10
A feature has been delivered but it doesn't meet the agreed requirements. Which phrase best describes this?
The acceptance criteria weren't met: Acceptance criteria are the agreed conditions a story must satisfy to be considered done. Using this phrase links the issue directly to the Definition of Done — the professional standard for delivery. It is objective and specific, which matters in QA reviews and sprint retrospectives. Option B is vague and informal. Option C assigns blame without evidence. Option D deflects responsibility to requirements, which is counterproductive. Always refer to acceptance criteria rather than vague expectations when raising quality issues.
3 / 10
A bug that was fixed in a previous release has appeared again. Which phrase is the standard way to describe this?
This is a regression from the last release: A regression is a specific testing term for functionality that previously worked correctly but has broken again — usually due to new changes introducing unintended side effects. Using "regression" immediately signals the nature of the defect, helps prioritise it, and tells developers to look at recent changes. Option A is informal and doesn't use the technical term. Option C is vague and non-technical. Option D sounds frustrated and unhelpful for triage. In professional QA, regressions are typically labelled in the bug tracker and assigned high priority.
4 / 10
You want to flag that a module doesn't have enough automated tests. Which phrasing is most appropriate?
The test coverage for this module is low: Test coverage is a measurable metric — typically expressed as a percentage of code lines, branches, or functions exercised by automated tests. Referring to it precisely is the professional approach in code reviews and QA discussions. Option A implies blame without being constructive. Option B introduces emotional language ("risky") without specifics. Option C is a vague personal worry rather than an objective observation. Mentioning test coverage naturally leads to action: checking coverage reports, writing unit tests, and adding the module to a testing backlog.
5 / 10
You want to flag an issue as one that must be fixed before release. Which phrase is correct?
I'd mark this as a blocker: In bug-tracking systems such as Jira, GitHub Issues, and Bugzilla, "blocker" is the highest severity/priority label — it means the release or a specific workflow cannot proceed until the issue is resolved. Using the correct label term is essential for clear communication between QA, developers, and product managers. Option A is emotional and non-specific. Option C is informal and doesn't use established severity terminology. Option D is unprofessional. Saying "I'd mark this" also shows ownership and initiative rather than just complaining.
6 / 10
Sarah: 'I've run the tests multiple times, and the error still appears. Can you confirm that the environment is set up correctly?' Which phrase best reflects Sarah's approach to debugging?
Sarah's response demonstrates a methodical approach. It's crucial to clearly document the steps taken during reproduction, as this allows others to understand the context and potentially identify the root cause more quickly. Options A and C are problematic because they lack specific details about the environment or how the bug is manifested. Option D is too passive.
7 / 10
Mark (in a Slack channel) reports: 'The API endpoint returns 500 when submitting a valid form. It works fine for me locally.' Which phrase best captures Mark's feedback and suggests the most appropriate next step?
Mark's message is incomplete; it needs more context to be truly helpful. Simply stating an error code doesn't pinpoint the cause. The response should emphasize the need for logs and details about the form data being submitted. A good response would ask for a screenshot of the API response, or a copy of the input data.
8 / 10
You're writing a pull request description for a new feature. The feature was designed to handle user authentication but unexpectedly allows users to bypass the password check. Which phrase is most appropriate to include?
Highlighting the security issue is paramount. It's not enough to simply state that the feature is complete; you must immediately draw attention to any potential vulnerabilities. The other options are irrelevant and could mask a serious problem. This response adheres to best practices for communicating critical issues in code reviews.
9 / 10
During a standup meeting, David says: 'I've been working on the new reporting module. It's functional, but it doesn't currently support exporting data to CSV.' Which phrase best describes David's status and suggests a necessary action?
David's statement clearly identifies a missing requirement. Simply stating that something is 'functional' isn't enough; it must be explicitly noted if it doesn't meet the specifications. This phrasing directly highlights the need for further development and prompts the team to prioritize the CSV export feature.
10 / 10
You're reviewing a code change that implements user profile updates. The developer has added validation but hasn't implemented any tests for the new validation rules. Which phrase best describes this situation?
The absence of tests is a critical issue. While validation is important, it's not sufficient without corresponding tests to confirm that the validation rules are working as expected and won't introduce regressions. This phrase directly flags the missing component for attention – robust code requires both validation *and* testing.
What will I practise in "QA & Testing Phrases: Reporting Bugs and Quality Issues"?
This module focuses on Phrasebook — real workplace phrasing you'll use on the job. It contains 10 scenario-based multiple-choice questions with instant feedback.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account or sign-up required.
How many questions does this exercise have?
This module includes 10 questions. Each one gives an immediate right/wrong result plus a full explanation of the correct phrasing.
What happens if I answer a question incorrectly?
You'll see the correct answer highlighted straight away, along with a plain-English explanation of why it's right and why the other options don't fit — mistakes are part of the learning here.
Can I retry the exercise if I want a better score?
Yes — use the 'Try again' button on the results screen to reset your score and go through the questions again. There's no limit on attempts.
Who is this Phrasebook exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around phrasebook — useful whether you're preparing for real conversations at work or just building confidence with the vocabulary.
Do I need an account to track my progress?
No account is needed. Your progress through the exercise is tracked locally in your browser for the current session, and you can replay the module at any time.
How is this different from reading a blog article?
This exercise is an interactive drill that tests and reinforces specific phrasing through multiple-choice questions with instant feedback, while blog articles explain concepts and vocabulary in prose. The two work well together.
Where can I find more Phrasebook exercises?
See the Phrasebook hub for more modules like this one, or browse the full Exercises page for other IT-English topics.
Can I complete this exercise on my phone?
Yes — every exercise on CoderSlingo is fully responsive and works on phones and tablets, so you can practise anywhere.