05 · Automation
E2E and API Automation: Playwright, TypeScript and CI
Build a test automation framework from an empty folder: UI journeys in Month 1, the API in Month 2, both running on every pull request in Month 3.
- 3 months · 48 h · 2 × 2 h a week
- Online, live
- max 10 participants
What you'll be able to do
- Automate real user journeys with Playwright: locators, web-first assertions, page objects and fixtures
- Log in once with saved auth state and keep test data isolated when ten people share one app
- Kill flakiness at the source: stable waits, races found and fixed, traces read
- Test a REST API with a typed client, Zod schemas, auth flows and contract checks
- Run the suite in GitHub Actions with sharding, retries, quarantine and readable reports
- Finish with a public framework repo and a green CI run a hiring manager can read
Program
Month 1 · UI automation with Playwright
The framework skeleton, locators, assertions, page objects and fixtures, auth state, test data strategy, stable waits, visual and accessibility checks.
Month 2 · API automation
HTTP and REST in practice, a typed request client, Zod schema validation, auth flows and negative cases, test data via the API, contract checks, boundary design and Qase reporting.
Month 3 · CI and the portfolio
GitHub Actions on every pull request, parallelism and sharding, retries and a flaky-test policy, reports, test selection on a diff, AI-assisted maintenance, and the portfolio project.
Who it's for
QA engineers who can read TypeScript and use a terminal. Graduates of Software Building and Testing start directly; everyone else takes a short self-check first.