Future / To Explore
Topics that belong in this track but are not written yet. Each one is a page I plan to add once I have used it on a real project. Until then, the official docs link is the best source.
API Testing with the request Fixture
Playwright ships an HTTP client with the same assertions. Use it to set up data before a UI test, to verify a backend effect after one, or to test an API on its own without a browser.
- Docs: https://playwright.dev/docs/api-testing
- Where it fits: a fixture that creates a record via API before
use()and deletes it after
Network Mocking
page.route() intercepts requests and returns canned responses. This is how you test error states (500 from the backend, slow responses) and how you cut third-party dependencies out of the test.
- Docs: https://playwright.dev/docs/mock
- Where it fits: Section 2's "avoid third-party dependencies" rule, made practical
Visual Comparison
expect(page).toHaveScreenshot() compares against a stored image. Powerful for layout regressions, fragile across machines and fonts. Needs a strategy for baselines before it goes into CI.
Aria Snapshots
toMatchAriaSnapshot() checks the accessibility tree of a region as YAML. More stable than screenshots, more meaningful than a single locator. Likely the first of these topics to become a page.
Test Agents
The planner, generator and healer agents introduced in 1.56. Worth a page once I have a clear view of where they help and where they generate tests nobody understands.
Component Testing
Testing a single React or Vue component in a real browser. Playwright's component testing packages were marked experimental and, as of 1.63, are no longer updated, so this is on hold.
The Playground App
Once the shared Docker playground exists, the sample tests move from saucedemo to it, and this track gets a "reset the data" section that the public demo cannot offer.