Playwright Resources
Official docs at playwright.dev stay current with each release — start there for anything not covered in depth here. These curated links are the bookmarks senior engineers keep open daily.
Where to Go Next The API reference documents every method on Page, Locator, BrowserContext, and the test runner. Release notes on GitHub explain breaking changes and new features like UI Mode improvements.
Tooling around Playwright — VS Code extension, Trace Viewer, Docker images, and GitHub Actions templates — covers the workflows that appear in almost every production setup.
playwright.dev/docs
playwright.dev/docs/api/class-test
github.com/microsoft/playwright
npm init playwright@latestOfficial docs beat third-party tutorials for version-accurate information.
Searching Docs Effectively site:playwright.dev getByRole
site:playwright.dev page.route storageState Search official docs directly — blog posts often lag new releases. API reference pages list every option for config and matchers. GitHub issues and discussions answer edge cases. Release notes highlight deprecations before you hit them in upgrades. Resources Reference Official and community resources worth bookmarking.
Resource Use For playwright.dev/docs Guides and getting started playwright.dev/docs/api Complete API reference VS Code extension Run, debug, pick locators in editor Trace Viewer Post-mortem CI failure replay Playwright Docker images Consistent CI environments microsoft/playwright GitHub Issues, releases, source Playwright Discord Community Q&A @axe-core/playwright Accessibility scanning
Official Documentation Map Navigate docs by task: "Writing tests", "Test configuration", "CI", "Component testing" — each guide links to relevant API pages.
Getting started — install, first test, codegen. Locators — role, text, filters, strict mode. Test configuration — projects, workers, reporters. Release notes — upgrade path between versions. Common Mistakes Following outdated tutorials that predate UI Mode or component testing. Never reading release notes before upgrading @playwright/test. Ignoring the VS Code extension and struggling with CLI-only workflows. Using random npm wrappers instead of documented Playwright APIs. Key Takeaways playwright.dev is the authoritative source for guides and API details. VS Code extension, Trace Viewer, and Docker images are core tooling. Check release notes when upgrading versions. Community Discord and GitHub issues help with edge cases.
Subscribe to GitHub releases on microsoft/playwright — skim each note for features that replace custom workarounds you maintain.
Playwright Cheat Sheet Go to next item