QA Automation

By the end you’ll be able to

• Decide what is worth automating, and say why the rest isn't
• Write Playwright tests with locators that survive a refactor
• Structure a suite that someone else can extend without asking you
• Run it in GitHub Actions on every pull request
• Publish results to TestForge and act on flakiness data

1. 01What is worth automatingThe pyramid, its critics, and the maintenance cost nobody budgets for.12 min
2. 02Programming foundations for testersVariables, functions, async, and reading someone else's code — JS/TS path.18 min
3. 03Your first Playwright testInstall, record, run, and understand every line of what you just wrote.Hands-on16 min
4. 04Locators that survive a refactorRoles, labels and test ids — and why CSS chains break every sprint.14 min
5. 05Assertions and waitingWeb-first assertions, auto-waiting, and why sleep() is a bug.13 min
6. 06Page objects, and when they hurtStructure that pays off, structure that becomes a second application.14 min
7. 07Test data and fixturesIndependent tests, seeded state, and cleaning up after yourself.13 min
8. 08API automationFaster, steadier tests below the UI — and using the API to set up UI tests.14 min
9. 09Running in CI with GitHub ActionsWorkflows, matrices, artifacts, and keeping the pipeline under ten minutes.Hands-on16 min
10. 10Capstone: publish results to TestForgeEmit JUnit XML, upload it via /api/v1/junit, and read the run you just created.Hands-on15 min
11. 11Flaky tests: diagnosis and quarantineFinding the cause, and muting honestly instead of retrying forever.14 min
12. 12Designing a framework you can hand overConfig, reporting, conventions, and the README that makes it survivable.15 min