Automation QA with Playwright
14 videosA step-by-step path for manual testers who want to become automation QA: from your first Playwright test to reliable tests running in CI.
Start here: Why automate tests? →Part 1 · From manual to automation
1:531Why automate tests?
What manual regression really costs, what is worth automating and what is not, where Playwright fits in the test pyramid, and why your test cases are the valuable part.
1:382Install Playwright and run your first test
Check Node, create a project with npm init playwright, tour the files it creates, run the example tests and open the HTML report.
1:383Anatomy of a test: from test case to code
Map a manual test case to a Playwright test: the title, the steps as awaited actions, the expected result as an assertion, and how a pass or a failure looks.
Part 2 · Locators, actions, assertions
1:394Locators: find elements like a user
How Playwright finds an element: getByRole, getByLabel, getByText and getByTestId, why long CSS and XPath chains break, and the order to prefer.
1:265Actions: click, fill, check and more
Every verb in a manual test case has a Playwright method: goto, click, fill, check, selectOption, hover, press and setInputFiles, and how Playwright acts like a real user.
1:256Assertions and auto-waiting
Write the expected result with expect, why fixed sleeps make tests slow and flaky, how Playwright waits automatically, and why web-first assertions retry.
Part 3 · Maintainable tests
1:217Structure your tests: describe, hooks, tags
Group tests with describe, share setup in beforeEach, keep every test independent in a fresh browser context, and pick what to run with tags like @smoke.
1:178Page Object Model
Stop repeating locators across tests: put each page's locators and actions in a class, so tests read like manual steps and a UI change is fixed in one place.
1:229Log in once, and use fixtures
Stop logging in through the form in every test: save the session as storage state in a setup project, reuse it in the config, and share helpers with fixtures.
1:2010API testing and mocking the network
Use the request fixture to prepare data through the API, and page.route to fake server responses so you can test empty lists, errors and slow responses.
Part 4 · Debug, fix and run in CI
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.
1:3314Your 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.