Web server | Playwright
Introduction| playwright.dev
The [WebSocket] class represents WebSocket connections within a page. It provides the ability to inspect and manipulate the data being transmitted and received.| playwright.dev
[Response] class represents responses which are received by page.| playwright.dev
Whenever the page sends a request for a network resource the following sequence of events are emitted by [Page]:| playwright.dev
APIResponse] class represents responses returned by [apiRequestContext.get() and similar methods.| playwright.dev
The [PageAssertions] class provides assertion methods that can be used to make assertions about the [Page] state in the tests.| playwright.dev
The [APIResponseAssertions] class provides assertion methods that can be used to make assertions about the [APIResponse] in the tests.| playwright.dev
Selectors can be used to install custom selector engines. See extensibility for more information.| playwright.dev
FrameLocator represents a view to the iframe on the page. It captures the logic sufficient to retrieve the iframe and locate elements in that iframe. FrameLocator can be created with either locator.contentFrame(), page.frameLocator() or locator.frameLocator() method.| playwright.dev
Whenever a network route is set up with page.route() or browserContext.route(), the Route object allows to handle the route.| playwright.dev
BrowserType provides methods to launch a specific browser instance or connect to an existing one. The following is a typical example of using Playwright to drive automation:| playwright.dev
The [LocatorAssertions] class provides assertion methods that can be used to make assertions about the [Locator] state in the tests.| playwright.dev
Locators are the central piece of Playwright's auto-waiting and retry-ability. In a nutshell, locators represent a way to find element(s) on the page at any moment. A locator can be created with the page.locator() method.| playwright.dev
FrameLocator represents a view to the iframe on the page. It captures the logic sufficient to retrieve the iframe and locate elements in that iframe. FrameLocator can be created with either locator.contentframe, page.framelocator() or locator.frame_locator() method.| playwright.dev
The [LocatorAssertions] class provides assertion methods that can be used to make assertions about the [Locator] state in the tests.| playwright.dev
Locators are the central piece of Playwright's auto-waiting and retry-ability. In a nutshell, locators represent a way to find element(s) on the page at any moment. A locator can be created with the Page.Locator() method.| playwright.dev
FrameLocator represents a view to the iframe on the page. It captures the logic sufficient to retrieve the iframe and locate elements in that iframe. FrameLocator can be created with either Locator.ContentFrame, Page.FrameLocator() or Locator.FrameLocator() method.| playwright.dev
This API is used for the Web API testing. You can use it to trigger API endpoints, configure micro-services, prepare environment or the service to your e2e test.| playwright.dev
TestInfo contains information about currently running test. It is available to test functions, test.beforeEach(), test.afterEach(), test.beforeAll() and test.afterAll() hooks, and test-scoped fixtures. TestInfo provides utilities to control test execution: attach files, update test timeout, determine which test is currently running and whether it was retried, etc.| playwright.dev
The GenericAssertions] class provides assertion methods that can be used to make assertions about any values in the tests. A new instance of [GenericAssertions] is created by calling [expect():| playwright.dev
A Browser is created via browserType.launch(). An example of using a [Browser] to create a [Page]:| playwright.dev
API for collecting and saving Playwright traces. Playwright traces can be opened in Trace Viewer after Playwright script runs.| playwright.dev
Playwright Test supports running multiple test projects at the same time. This is useful for running tests in multiple configurations. For example, consider running tests against multiple browsers. This type describes format of a project in the configuration file, to access resolved configuration parameters at run time use [FullProject].| playwright.dev
BrowserContexts provide a way to operate multiple independent browser sessions.| playwright.dev
Page provides methods to interact with a single tab in a Browser], or an [extension background page in Chromium. One [Browser] instance might have multiple [Page] instances.| playwright.dev
BrowserContexts provide a way to operate multiple independent browser sessions.| playwright.dev
Cross-browser end-to-end testing for modern web apps| playwright.dev
Playwright Test provides a test function to declare tests and expect function to write assertions.| playwright.dev
Locators are the central piece of Playwright's auto-waiting and retry-ability. In a nutshell, locators represent a way to find element(s) on the page at any moment. A locator can be created with the page.locator() method.| playwright.dev
Playwright Test has multiple configurable timeouts for various tasks.| playwright.dev
Playwright Test provides many options to configure how your tests are collected and executed, for example timeout or testDir. These options are described in the TestConfig] object in the [configuration file. This type describes format of the configuration file, to access resolved configuration parameters at run time use [FullConfig].| playwright.dev
Playwright provides methods for comparing page and element screenshots with expected values stored in files.| playwright.dev
The [PageAssertions] class provides assertion methods that can be used to make assertions about the [Page] state in the tests.| playwright.dev
The [LocatorAssertions] class provides assertion methods that can be used to make assertions about the [Locator] state in the tests.| playwright.dev
BrowserType provides methods to launch a specific browser instance or connect to an existing one. The following is a typical example of using Playwright to drive automation:| playwright.dev
Page provides methods to interact with a single tab in a Browser], or an [extension background page in Chromium. One [Browser] instance might have multiple [Page] instances.| playwright.dev
BrowserContexts provide a way to operate multiple independent browser sessions.| playwright.dev
Page provides methods to interact with a single tab in a Browser], or an [extension background page in Chromium. One [Browser] instance might have multiple [Page] instances.| playwright.dev
BrowserContexts provide a way to operate multiple independent browser sessions.| playwright.dev
Cross-browser end-to-end testing for modern web apps| playwright.dev
Page provides methods to interact with a single tab in a Browser], or an [extension background page in Chromium. One [Browser] instance might have multiple [Page] instances.| playwright.dev
