playwright-python

Playwright Python tests use the pytest-playwright package, which provides page and context fixtures. You write test functions that use locators like page.get_by_role() to interact with elements and expect() assertions to verify page state.

Playwright lets you save authenticated state with browser_context.storage_state(path="state.json") after logging in once. New browser contexts can then be created with storage_state="state.json" to skip the login step in every test.

Yes, Playwright for Python provides both a synchronous API via playwright.sync_api and an asyncio-based API via playwright.async_api. Both expose the same classes and methods, differing only in await usage.

Yes, the APIRequestContext class sends HTTP requests directly without launching a browser. You create it via playwright.request.new_context() and use methods like get, post, and delete to test server APIs or prepare test state.

Playwright auto-waits for actionability checks such as visibility, stability, and enabled state before acting on elements. A TimeoutError means these checks did not pass within the configured timeout, often due to incorrect locators or elements obscured by overlays.

Playwright provides official Docker images and CI guides for GitHub Actions, Azure Pipelines, and GitLab CI. The core/ci.mdx and core/docker.mdx references cover installing browser dependencies and configuring pipelines.