Your automation plan
A practical plan for a manual tester becoming automation QA: start with ten smoke tests, build them well, triage failures as product bug, test bug or environment, and grow each sprint.
Transcript
You do not need to automate everything. Start small. Pick your ten most important checks: log in, search, add to cart, check out. These are your smoke tests.
Write them one at a time. Role and label locators, an expect for every expected result, and a page object when you repeat yourself. Review each test like production code.
Run them on every pull request. When a test fails, that is information. Ask: is it a product bug, a test bug, or an environment problem?
A product bug: report it, with the trace attached. A test bug: fix the test. An environment problem: fix the setup. Never just retry it away.
Then grow. Add a few tests every sprint, delete the tests that no longer matter, and keep the suite fast and green.
Remember: start with ten tests, run them on every pull request, treat each failure as information, and grow a little every sprint.
More in this series
1:2711Debugging tools: UI mode, codegen, inspector, trace
Find out why a test fails: UI mode with a timeline of snapshots, codegen to draft locators, the inspector to step through, and the trace viewer for failures in CI.
1:2412Flaky tests: find the cause, fix it
What a flaky test is, the usual causes (fixed sleeps, shared data, fragile locators, timing), how to fix each one, and why retries are a safety net, not a cure.
1:2113Reports and running tests in CI
Run Playwright on every pull request with GitHub Actions, run tests in parallel across workers and browsers, and keep the HTML report and traces as artifacts.