30-Day English for QA Engineers
Complete Learning Path

The path covers QA testing vocabulary, bug report writing, severity and priority language, test plan documentation, Given-When-Then acceptance criteria, BDD and Gherkin language, defect lifecycle communication, automation testing vocabulary, API testing, and technical interview preparation — all the English a QA engineer needs to work effectively in an international team.

Yes. The path is designed for both manual and automation QA engineers. Days 1–10 and 16–20 cover testing fundamentals and communication patterns applicable to both. Days 11–15 and 21–24 focus more on automation-specific vocabulary and test strategy language, which will be most valuable for automation engineers.

Days 2, 3, and 18 focus on bug report language: writing clear reproduction steps, describing expected vs. actual behaviour, assigning severity (critical, major, minor, trivial) and priority (P1, P2, P3), and using the precise vocabulary for different defect types — regression, showstopper, edge case, flaky test, intermittent failure, and more.

Yes. Days 5 and 6 focus specifically on Given-When-Then acceptance criteria and BDD/Gherkin language: writing scenarios in plain English, using the correct Feature/Scenario/Step keywords, combining Given-When-Then with And and But, and discussing BDD workflows with developers and product owners in planning sessions.

Yes. Day 13 covers test automation framework language: test runner, assertion library, fixture, mock, stub, spy, page object model, locator/selector, flaky test, retry logic, parallel execution, and the vocabulary used when discussing automation architecture with the engineering team.

Yes. Day 21 focuses on API testing language: endpoint, request body, response body, payload, status code, contract testing, schema validation, mock server, Postman collection, and the vocabulary used when writing API test plans and discussing API coverage with backend developers.

Yes. The path is marked Beginner–Intermediate and is designed to be approachable for junior QA engineers who are new to working in English-speaking teams. Week 1 starts with fundamental vocabulary and progressively introduces more advanced topics. If you are completely new to IT English, spend extra time on Days 1–5 before moving forward.

Yes. Day 7 focuses on the defect lifecycle: open, in progress, ready for testing, closed, won't fix, duplicate, cannot reproduce, deferred, reopened — and the language used when discussing defect status in daily standups, sprint reviews, and Jira comments with the development team.

Weeks three and five focus on communication: standup phrases, sprint review and demo language, formal defect report writing, async Slack communication, test coverage reporting, and technical interview preparation. QA engineers communicate regularly with developers, product managers, and stakeholders — the path covers all these communication contexts.

After the 30-day path, explore the QA Engineer guide at /guides/qa-engineer/ for comprehensive reference material, or browse /exercises/testing-qa-lab/ for additional testing exercises. If your role involves automation engineering, the Backend Developer path is a useful complement for understanding the code you are testing.