QA & Testing
QA engineers write more English than most IT roles — bug reports, test plans, UAT results, and release sign-offs. This path focuses on precise, unambiguous quality documentation language.
Topics covered
- Bug report writing
- Test case documentation
- QA communication
- Test automation vocabulary
- User acceptance testing
Vocabulary spotlight
4 terms every QA & Testing should know in English:
regression n.
A previously working feature that has broken after a code change
"This looks like a regression — the checkout flow was working in the last release."
flaky test n.
A test that sometimes passes and sometimes fails without code changes
"We have 12 flaky tests causing noise in CI."
smoke test n.
A quick surface-level check that a build is stable enough for further testing
"Run the smoke tests first before starting full regression."
severity vs. priority n.
Severity = impact of the bug; Priority = urgency to fix it
"High-severity, low-priority: it's bad but only affects an edge case."
📚 Vocabulary Reference
Key terms organised by category for QA & Testings:
Test Types
Test Anatomy
Bug Lifecycle
Test Tooling
QA Process
Recommended exercises
Agile & QA Vocabulary
Vocabulary QA & Testing Vocabulary
Vocabulary Testing Collocations
Vocabulary Bug Report Writing
Writing Test Case Documentation
Writing Reading Bug Reports & Jira Tickets
Reading Writing Bug Reports
Writing Writing Acceptance Criteria (Given/When/Then)
Writing QA Engineer Interview Questions
Interview Real-world scenarios you'll practise
- Writing a clear, reproducible bug report for developers
- Communicating a no-go release decision to the product manager
- Presenting test coverage metrics to stakeholders
- Writing a UAT sign-off document
Recommended reading
Reference glossaries for QA & Testings
Deep-dive glossaries covering terminology specific to this role: