Playwright

Playwright Test is the recommended first-party test runner for Playwright. It offers several 'super powers' compared to standard Puppeteer setups:

• Zero-config TypeScript: Full support out of the box.
• Cross-Engine/OS Testing: Run tests across all web engines (Chromium, Firefox, WebKit) on any major OS (Windows, macOS, Ubuntu).
• Isolation & Parallelism: Run tests in isolation and in parallel across multiple browsers.
• Advanced Features: Built-in support for multiple origins, iframes, tabs, and contexts.
• Tooling Bundle: Includes the Playwright Inspector, Test Code Generation (codegen), and Playwright Tracing for post-mortem debugging.
• Artifact Collection: Built-in recording of test artifacts.

The playwright-webkit package provides the WebKit browser engine implementation for Playwright.

Note: If your goal is to write end-to-end tests, it is highly recommended to use @playwright/test instead of this package directly, as @playwright/test provides a comprehensive test runner and framework built on top of Playwright.

Playwright allows you to interact directly with a REST API using the APIRequestContext class. This is useful for:

• Testing your server's API directly.
• Preparing server-side state (e.g., creating users or data) before running browser-based tests.
• Validating server-side post-conditions after performing actions in the browser.

These examples assume you are using the pytest-playwright package, which provides Playwright fixtures to the Pytest test runner.

Playwright supports multiple programming languages that share the same underlying browser automation implementation. While all core features are available across all languages, the testing ecosystem and recommended runners vary:

• JavaScript/TypeScript: Use the built-in Playwright Test runner for features like parallelization, screenshot assertions, HTML reporting, and automatic tracing.
• Python: Use the Playwright Pytest plugin for context isolation and multi-browser configuration support.
• Java: Compatible with standard frameworks like JUnit or TestNG.
• .NET: Provides base classes for MSTest, NUnit, xUnit, and xUnit v3.

The playwright-chromium package provides the Chromium flavor of the Playwright library. It is intended for direct automation of Chromium-based browsers.

Note: If your goal is to write end-to-end tests, it is highly recommended to use @playwright/test instead of this package, as it provides a more comprehensive testing framework.

The playwright-firefox package provides the Firefox implementation of the Playwright library.

Note: If your goal is to write end-to-end tests, it is highly recommended to use @playwright/test instead of using this package directly. @playwright/test provides a comprehensive test runner and framework built on top of Playwright's browser implementations.

Locators are the central piece of Playwright's auto-waiting and retry-ability. They represent a way to find element(s) on the page at any moment. You can create a locator using the Page.locator method.

Locators do not represent a single element at a specific point in time, but rather a way to find elements that Playwright will automatically wait for and retry against when performing actions.

A Page refers to a single tab or a popup window within a BrowserContext. You use it to navigate to URLs and interact with page content (e.g., filling inputs, clicking elements).

Key operations:

• Create a page: Use context.newPage().
• Explicit navigation: Use page.goto(url) to navigate to a specific URL.
• Implicit navigation: Trigger navigation by interacting with elements, such as page.locator(selector).click().
• Get current URL: Use page.url() to retrieve the current URL of the page.

// Create a page.
const page = await context.newPage();

// Navigate explicitly
await page.goto('http://example.com');

// Fill an input
await page.locator('#search').fill('query');

// Navigate implicitly by clicking a link
await page.locator('#submit').click();

// Get current url
console.log(page.url());