-
Phase 1. Where to start
Why this program exists and who it fits: what the ten phases hold, how tests and trainers work, and how to run the demo service from GitHub so there is something to test.
- Зачем этот курс required
-
Phase 2. What testing is · 30 questions
Why software is tested, the QA role, manual vs automated, the software and testing lifecycle.
- What Testing Is and Why It's Needed required
- Who a Tester Is and Their Role on the Team
- Testing Myths and What You Actually Need to Start
- Manual and Automated Testing: What's the Difference required
- The Software Lifecycle and Where Testing Fits (SDLC and STLC) required
- Software Development Models: Waterfall, V-Model, and Iterations
- Phase test in the cabinet
-
Phase 3. Types and levels · 30 questions
Test levels, functional and non-functional, black/white box, smoke and regression.
- Test Levels: Unit, Integration, System, and Acceptance required
- Types of Testing: Functional and Non-Functional required
- Non-Functional Testing Types in Practice required
- Black Box, White Box, and Grey Box; Smoke, Regression, and Sanity required
- Exploratory Testing and Degrees of Formalization required
- Localization Testing
- Phase test in the cabinet
-
Phase 4. Test-case design · 40 questions
Writing test cases, the test plan and suites, reporting and metrics, effort estimation, test-design techniques, decision tables, checklists and data.
- How to write a test case: steps and expected result required
- Test Case Quality: Balances, Fault-Finding Power, and Typical Mistakes
- Test plan and test suites: how to organize your checks required
- Test Result Reporting and Metrics required
- Effort Estimation in Testing
- Test design techniques: equivalence classes and boundary values required
- Decision tables and pairwise testing required
- Checklists and test data required
- User Scenarios, Personas, and Test Case Suites
- Phase test in the cabinet
-
Phase 5. Bugs · 22 questions
What a bug is, severity and priority, writing a bug report and making it high-quality, the bug lifecycle and trackers.
-
Phase 6. Tools and practice · 68 questions
Test management, web basics (HTML/CSS/JS), client-server and HTTP, DevTools, API in Postman, SQL, cross-browser testing and Linux commands.
- Test Management: TestRail, Qase, Zephyr
- Web Basics: HTML, CSS, JavaScript, and the DOM
- Client-Server and HTTP: How a Page Talks to a Server required
- Browser DevTools for Testers required
- API Testing Basics in Postman required
- API styles for testers: REST, SOAP and GraphQL required
- Networking basics: how a request finds the server required
- Logging in: authentication, authorization and tokens required
- IDOR и BOLA
- Как искать уязвимости
- SQL for Testers required
- Cross-Browser and Mobile Testing
- Mobile app testing
- Linux Commands and the Terminal for Testers
- Logs and monitoring for testers required
- Data formats for testers: JSON, XML, YAML and CSV required
- Microservices, brokers and queues through a tester's eyes required
- What Docker and Containers Are required
- Phase test in the cabinet
-
Phase 7. SQL from scratch · 50 questions
A standalone SQL series with no prerequisites: databases and tables, SELECT, JOIN, aggregates, NULL, subqueries, window functions, dates and strings, modifying data, creating tables and indexes.
- What a Database and Tables Are
- SELECT: Pick, Filter, Sort required
- JOIN: Combine Data from Several Tables required
- Aggregates: COUNT, GROUP BY and HAVING required
- NULL and Data Types: Where Everyone Stumbles required
- Subqueries and CTEs: A Query Inside a Query required
- Window Functions: Counting Without Collapsing Rows required
- Даты и время
- Строки
- INSERT, UPDATE, DELETE and Transactions
- Database Schema: Tables, Keys and Views required
- Why a Query Is Slow: Indexes on Your Fingers required
- Mock interview in the cabinet
- Phase test in the cabinet
-
Phase 8. Python for autotests · 43 questions
Python from scratch to autotests: variables and strings, conditions, lists and dicts, loops, functions, assert, working with data, pytest and API autotests. Every article comes with trainer tasks.
- Why a Tester Needs Python and How to Run the First Line
- Variables, Strings and Numbers required
- Comparisons and Conditions: How a Program Decides
- Lists and Dicts: JSON Is a Dict required
- Loops: Go Through Everything and Miss Nothing required
- Functions: Keep a Check in One Place required
- assert and Errors: How a Check Reports a Break
- Working with Data: Count, Compare, Find the Difference
- pytest: Your First Real Test required
- API Autotests in Python: Putting It Together required
- Mock interview in the cabinet
- Phase test in the cabinet
-
Phase 9. UI end-to-end tests · 42 questions
Playwright: when an end-to-end test is worth it, setup, test structure and page objects, resilient locators, waiting instead of sleeps, data and login without the form, network interception, flakiness and CI runs.
- Когда нужен e2e required
- Настройка
- Структура тестов required
- Локаторы required
- Утверждения и ожидание required
- Данные и аутентификация
- Сеть
- Нестабильные тесты required
- E2E в CI required
- Phase test in the cabinet
-
Phase 10. On a team and beyond · 41 questions
QA in Agile and Scrum, testing against requirements, automation basics and where to grow next.
- QA in Agile and Scrum: your role in a sprint required
- Testing against requirements required
- Requirement Levels and the Properties of Good Requirements
- Requirements Review: Techniques and Good Questions
- How Automation Works: Approaches and Economics required
- Git for testers: branches, commits and merges required
- CI/CD: The Pipeline, Tests and Artifacts
- Where to grow as a tester
- Phase test in the cabinet
-
Phase 11. Development methodologies and process · 28 questions
Waterfall, Agile, Scrum, Kanban, XP, estimation and scaling — how a team organizes work from idea to release.
Программа обучения v3.16.6
QA engineer
The whole tester path in one program: from «what is testing» through test types and levels, test-case design and bug work to tools — Postman, DevTools, SQL — and autotests: first API in Python, then the UI in Playwright. It closes with teamwork and development methodologies.
The program has 394 self-check questions in total.