Playwright, pytest, Page Object Model, AI test generation, visual regression, and CI gates — 100 challenges to build a production automation suite.
Learn to build and maintain a production-grade automated test suite using Playwright (TypeScript) and pytest (Python). Start with the test pyramid and ROI of automation, master Playwright for E2E testing (selectors, POM, fixtures, network mocking), use AI to generate and maintain test cases, set up visual regression, integrate into GitHub Actions CI with quality gates, manage test data at scale, automate performance budgets, and understand consumer-driven contract testing. Every module has working code that runs today, and a project that becomes a portfolio piece.
Built by Lakshya Kumar
We grant free access case-by-case — students, career-switchers, builders on a tight budget. Sign in to send us a note.
Sign in to applyComplete all modules, then submit the required number of capstone projects. Each must earn a passing rating from an admin reviewer.
Build a complete Playwright test suite for a web application (real or demo). Must include: 30+ test cases in Page Object Model, API mocking for at least one test scenario, visual regression for 3 key page states, GitHub Actions CI that blocks merges when tests fail, test data management (unique data per test run), and at least 5 test cases generated using AI prompts (documented in the README). Zero flaky tests over 5 consecutive CI runs.
Paste this into any AI chat. Fill in the bracketed parts with your context — you'll get back a straight answer on whether this belongs on your plate.
I'm considering 'Automated QA with AI' — a course on building production-grade test automation with Playwright, pytest, Page Object Model, AI test generation, visual regression, CI quality gates, and self-healing tests. 100 challenges in JavaScript/TypeScript and Python. Context: 1. My current automation experience: [e.g. "never written an automated test", "written some Selenium tests", "comfortable with pytest", "write Playwright tests but they're flaky"] 2. My programming background: [e.g. "JavaScript developer", "Python tester", "no coding background", "can read code but not write from scratch"] 3. What I want to build: [e.g. "CI pipeline that blocks bad deploys", "replace 200 manual regression cases", "portfolio piece for SDET job applications", "test suite for my startup"] Answer: - Which 2 modules will give me the highest leverage in the next 3 months? - What will I have built by the end that I can show in a job interview? - Should I do QA Fundamentals first, or can I start here? - What will I NOT be able to do after — e.g. "test mobile native apps", "write API contract tests", "build a full observability platform"?
Pick a real module (auth, payment, or similar). Use an LLM to generate test cases from the source code + specifications. Run the generated tests; measure mutation-testing kill rate. Compare against human-written tests for the same module.
Run an existing test suite N times; identify flaky tests (intermittent failures). For each flaky test, diagnose root cause (race condition, dependency on time, env-specific). Fix or quarantine at least 5; document the policy for flaky-test handling.
Set up a visual regression pipeline (Percy, Chromatic, or DIY with pixelmatch): screenshot critical screens on every PR, compare against baseline, surface diffs. Apply to at least 10 screens; demonstrate catching a deliberate visual regression.
Build a system that uses an LLM to triage incoming bug reports: classify severity, identify duplicates, route to the right team. Evaluate on 100 historical bug reports; report accuracy vs human triage.
Real practices from Google's engineering team. The test pyramid article is essential.