id | title | toc_max_heading_level |
---|---|---|
release-notes |
Release notes |
2 |
-
New method [
method: LocatorAssertions.toContainClass
] to ergonomically assert individual class names on the element.await Expect(Page.GetByRole(AriaRole.Listitem, new() { Name = "Ship v1.52" })).ToContainClassAsync("done");
-
Aria Snapshots got two new properties:
/children
for strict matching and/url
for links.await Expect(locator).ToMatchAriaSnapshotAsync(@" - list - /children: equal - listitem: Feature A - listitem: - link ""Feature B"": - /url: ""https://playwright.dev"" ");
- New option [
option: APIRequest.newContext.maxRedirects
] in [method: APIRequest.newContext
] to control the maximum number of redirects. - New option [
option: Locator.ariaSnapshot.ref
] in [method: Locator.ariaSnapshot
] to generate reference for each element in the snapshot which can later be used to locate the element. - HTML reporter now supports NOT filtering via
!@my-tag
or!my-file.spec.ts
or!p:my-project
.
- Base URL matching is not supported in [
method: Page.frame
] anymore. We recommend migrating to [method: Page.frameLocator
] instead for having a more convenient API. - Glob URL patterns in methods like [
method: Page.route
] do not support?
and[]
anymore. We recommend using regular expressions instead. - Method [
method: Route.continue
] does not allow to override theCookie
header anymore. If aCookie
header is provided, it will be ignored, and the cookie will be loaded from the browser's cookie store. To set custom cookies, use [method: BrowserContext.addCookies
]. - macOS 13 is now deprecated and will no longer receive WebKit updates. Please upgrade to a more recent macOS version to continue benefiting from the latest WebKit improvements.
- Chromium 136.0.7103.25
- Mozilla Firefox 137.0
- WebKit 18.4
This version was also tested against the following stable channels:
- Google Chrome 135
- Microsoft Edge 135
-
New option [
option: BrowserContext.storageState.indexedDB
] for [method: BrowserContext.storageState
] allows to save and restore IndexedDB contents. Useful when your application uses IndexedDB API to store authentication tokens, like Firebase Authentication.Here is an example following the authentication guide:
// Save storage state into the file. Make sure to include IndexedDB. await context.StorageStateAsync(new() { Path = "../../../playwright/.auth/state.json", IndexedDB = true }); // Create a new context with the saved storage state. var context = await browser.NewContextAsync(new() { StorageStatePath = "../../../playwright/.auth/state.json" });
-
New option [
option: Locator.filter.visible
] for [method: Locator.filter
] allows matching only visible elements.// Ignore invisible todo items. var todoItems = Page.GetByTestId("todo-item").Filter(new() { Visible = true }); // Check there are exactly 3 visible ones. await Expect(todoItems).ToHaveCountAsync(3);
-
New option
Contrast
for methods [method: Page.emulateMedia
] and [method: Browser.newContext
] allows to emulate theprefers-contrast
media feature. -
New option [
option: APIRequest.newContext.failOnStatusCode
] makes all fetch requests made through the [APIRequestContext] throw on response codes other than 2xx and 3xx.
- Chromium 134.0.6998.35
- Mozilla Firefox 135.0
- WebKit 18.4
This version was also tested against the following stable channels:
- Google Chrome 133
- Microsoft Edge 133
- Support for xUnit 2.8+ via Microsoft.Playwright.Xunit. Follow our Getting Started guide to learn more.
- Added method [
method: LocatorAssertions.toHaveAccessibleErrorMessage
] to assert the Locator points to an element with a given aria errormessage.
- New button in Codegen for picking elements to produce aria snapshots.
- Additional details (such as keys pressed) are now displayed alongside action API calls in traces.
- Display of
canvas
content in traces is error-prone. Display is now disabled by default, and can be enabled via theDisplay canvas content
UI setting. Call
andNetwork
panels now display additional time information.
- [
method: LocatorAssertions.toBeEditable
] and [method: Locator.isEditable
] now throw if the target element is not<input>
,<select>
, or a number of other editable elements.
- Chromium 133.0.6943.16
- Mozilla Firefox 134.0
- WebKit 18.2
This version was also tested against the following stable channels:
- Google Chrome 132
- Microsoft Edge 132
New assertion [method: LocatorAssertions.toMatchAriaSnapshot
] verifies page structure by comparing to an expected accessibility tree, represented as YAML.
await page.GotoAsync("https://playwright.dev");
await Expect(page.Locator("body")).ToMatchAriaSnapshotAsync(@"
- banner:
- heading /Playwright enables reliable/ [level=1]
- link ""Get started""
- link ""Star microsoft/playwright on GitHub""
- main:
- img ""Browsers (Chromium, Firefox, WebKit)""
- heading ""Any browser • Any platform • One API""
");
You can generate this assertion with Test Generator or by calling [method: Locator.ariaSnapshot
].
Learn more in the aria snapshots guide.
New method [method: Tracing.group
] allows you to visually group actions in the trace viewer.
// All actions between GroupAsync and GroupEndAsync
// will be shown in the trace viewer as a group.
await Page.Context.Tracing.GroupAsync("Open Playwright.dev > API");
await Page.GotoAsync("https://playwright.dev/");
await Page.GetByRole(AriaRole.Link, new() { Name = "API" }).ClickAsync();
await Page.Context.Tracing.GroupEndAsync();
This change affects you if you're using one of the following channels in your playwright.config.ts
:
chrome
,chrome-dev
,chrome-beta
, orchrome-canary
msedge
,msedge-dev
,msedge-beta
, ormsedge-canary
After updating to Playwright v1.49, run your test suite. If it still passes, you're good to go. If not, you will probably need to update your snapshots, and adapt some of your test code around PDF viewers and extensions. See issue #33566 for more details.
You can opt into the new headless mode by using 'chromium'
channel. As official Chrome documentation puts it:
New Headless on the other hand is the real Chrome browser, and is thus more authentic, reliable, and offers more features. This makes it more suitable for high-accuracy end-to-end web app testing or browser extension testing.
See issue #33566 for the list of possible breakages you could encounter and more details on Chromium headless. Please file an issue if you see any problems after opting in.
<?xml version="1.0" encoding="utf-8"?>
<RunSettings>
<Playwright>
<BrowserName>chromium</BrowserName>
<LaunchOptions>
<Channel>chromium</Channel>
</LaunchOptions>
</Playwright>
</RunSettings>
dotnet test -- Playwright.BrowserName=chromium Playwright.LaunchOptions.Channel=chromium
- There will be no more updates for WebKit on Ubuntu 20.04 and Debian 11. We recommend updating your OS to a later version.
<canvas>
elements inside a snapshot now draw a preview.
- Chromium 131.0.6778.33
- Mozilla Firefox 132.0
- WebKit 18.2
This version was also tested against the following stable channels:
- Google Chrome 130
- Microsoft Edge 130
New methods [method: Page.routeWebSocket
] and [method: BrowserContext.routeWebSocket
] allow to intercept, modify and mock WebSocket connections initiated in the page. Below is a simple example that mocks WebSocket communication by responding to a "request"
with a "response"
.
await page.RouteWebSocketAsync("/ws", ws => {
ws.OnMessage(frame => {
if (frame.Text == "request")
ws.Send("response");
});
});
See [WebSocketRoute] for more details.
- New "copy" buttons for annotations and test location in the HTML report.
- Route method calls like [
method: Route.fulfill
] are not shown in the report and trace viewer anymore. You can see which network requests were routed in the network tab instead. - New "Copy as cURL" and "Copy as fetch" buttons for requests in the network tab.
- New method [
method: Page.requestGC
] may help detect memory leaks. - Requests made by [APIRequestContext] now record detailed timing and security information in the HAR.
- Chromium 130.0.6723.19
- Mozilla Firefox 130.0
- WebKit 18.0
This version was also tested against the following stable channels:
- Google Chrome 129
- Microsoft Edge 129
The Network tab in the trace viewer has several nice improvements:
- filtering by asset type and URL
- better display of query string parameters
- preview of font assets
- The
mcr.microsoft.com/playwright/dotnet:v1.47.0
now serves a Playwright image based on Ubuntu 24.04 Noble. To use the 22.04 jammy-based image, please usemcr.microsoft.com/playwright/dotnet:v1.47.0-jammy
instead. - The
:latest
/:focal
/:jammy
tag for Playwright Docker images is no longer being published. Pin to a specific version for better stability and reproducibility. - TLS client certificates can now be passed from memory by passing [
option: Browser.newContext.clientCertificates.cert
] and [option: Browser.newContext.clientCertificates.key
] as byte arrays instead of file paths. - [
option: Locator.selectOption.noWaitAfter
] in [method: Locator.selectOption
] was deprecated. - We've seen reports of WebGL in Webkit misbehaving on GitHub Actions
macos-13
. We recommend upgrading GitHub Actions tomacos-14
.
- Chromium 129.0.6668.29
- Mozilla Firefox 130.0
- WebKit 18.0
This version was also tested against the following stable channels:
- Google Chrome 128
- Microsoft Edge 128
Playwright now allows to supply client-side certificates, so that server can verify them, as specified by TLS Client Authentication.
You can provide client certificates as a parameter of [method: Browser.newContext
] and [method: APIRequest.newContext
]. The following snippet sets up a client certificate for https://example.com
:
var context = await Browser.NewContextAsync(new() {
ClientCertificates = [
new() {
Origin = "https://example.com",
CertPath = "client-certificates/cert.pem",
KeyPath = "client-certificates/key.pem",
}
]
});
- Content of text attachments is now rendered inline in the attachments pane.
- New setting to show/hide routing actions like [
method: Route.continue
]. - Request method and status are shown in the network details tab.
- New button to copy source file location to clipboard.
- Metadata pane now displays the
BaseURL
.
- New
maxRetries
option in [method: APIRequestContext.fetch
] which retries on theECONNRESET
network error.
- Chromium 128.0.6613.18
- Mozilla Firefox 128.0
- WebKit 18.0
This version was also tested against the following stable channels:
- Google Chrome 127
- Microsoft Edge 127
Utilizing the new [Clock] API allows to manipulate and control time within tests to verify time-related behavior. This API covers many common scenarios, including:
- testing with predefined time;
- keeping consistent time and timers;
- monitoring inactivity;
- ticking through time manually.
// Initialize clock with some time before the test time and let the page load naturally.
// `Date.now` will progress as the timers fire.
await Page.Clock.InstallAsync(new()
{
TimeDate = new DateTime(2024, 2, 2, 8, 0, 0)
});
await Page.GotoAsync("http://localhost:3333");
// Pretend that the user closed the laptop lid and opened it again at 10am.
// Pause the time once reached that point.
await Page.Clock.PauseAtAsync(new DateTime(2024, 2, 2, 10, 0, 0));
// Assert the page state.
await Expect(Page.GetByTestId("current-time")).ToHaveTextAsync("2/2/2024, 10:00:00 AM");
// Close the laptop lid again and open it at 10:30am.
await Page.Clock.FastForwardAsync("30:00");
await Expect(Page.GetByTestId("current-time")).ToHaveTextAsync("2/2/2024, 10:30:00 AM");
See the clock guide for more details.
-
Method [
method: Locator.setInputFiles
] now supports uploading a directory for<input type=file webkitdirectory>
elements.await page.GetByLabel("Upload directory").SetInputFilesAsync("mydir");
-
Multiple methods like [
method: Locator.click
] or [method: Locator.press
] now support aControlOrMeta
modifier key. This key maps toMeta
on macOS and maps toControl
on Windows and Linux.// Press the common keyboard shortcut Control+S or Meta+S to trigger a "Save" operation. await page.Keyboard.PressAsync("ControlOrMeta+S");
-
New property
httpCredentials.send
in [method: APIRequest.newContext
] that allows to either always send theAuthorization
header or only send it in response to401 Unauthorized
. -
Playwright now supports Chromium, Firefox and WebKit on Ubuntu 24.04.
-
v1.45 is the last release to receive WebKit update for macOS 12 Monterey. Please update macOS to keep using the latest WebKit.
- Chromium 127.0.6533.5
- Mozilla Firefox 127.0
- WebKit 17.4
This version was also tested against the following stable channels:
- Google Chrome 126
- Microsoft Edge 126
Accessibility assertions
-
[
method: LocatorAssertions.toHaveAccessibleName
] checks if the element has the specified accessible name:var locator = Page.GetByRole(AriaRole.Button); await Expect(locator).ToHaveAccessibleNameAsync("Submit");
-
[
method: LocatorAssertions.toHaveAccessibleDescription
] checks if the element has the specified accessible description:var locator = Page.GetByRole(AriaRole.Button); await Expect(locator).ToHaveAccessibleDescriptionAsync("Upload a photo");
-
[
method: LocatorAssertions.toHaveRole
] checks if the element has the specified ARIA role:var locator = Page.GetByTestId("save-button"); await Expect(locator).ToHaveRoleAsync(AriaRole.Button);
Locator handler
- After executing the handler added with [
method: Page.addLocatorHandler
], Playwright will now wait until the overlay that triggered the handler is not visible anymore. You can opt-out of this behavior with the newNoWaitAfter
option. - You can use new
Times
option in [method: Page.addLocatorHandler
] to specify maximum number of times the handler should be run. - The handler in [
method: Page.addLocatorHandler
] now accepts the locator as argument. - New [
method: Page.removeLocatorHandler
] method for removing previously added locator handlers.
var locator = Page.GetByText("This interstitial covers the button");
await Page.AddLocatorHandlerAsync(locator, async (overlay) =>
{
await overlay.Locator("#close").ClickAsync();
}, new() { Times = 3, NoWaitAfter = true });
// Run your tests that can be interrupted by the overlay.
// ...
await Page.RemoveLocatorHandlerAsync(locator);
Miscellaneous options
-
New method [
method: FormData.append
] allows to specify repeating fields with the same name inMultipart
option inAPIRequestContext.FetchAsync()
:var formData = Context.APIRequest.CreateFormData(); formData.Append("file", new FilePayload() { Name = "f1.js", MimeType = "text/javascript", Buffer = System.Text.Encoding.UTF8.GetBytes("var x = 2024;") }); formData.Append("file", new FilePayload() { Name = "f2.txt", MimeType = "text/plain", Buffer = System.Text.Encoding.UTF8.GetBytes("hello") }); var response = await Context.APIRequest.PostAsync("https://example.com/uploadFiles", new() { Multipart = formData });
-
[
method: PageAssertions.toHaveURL
] now supportsIgnoreCase
option.
- Chromium 125.0.6422.14
- Mozilla Firefox 125.0.1
- WebKit 17.4
This version was also tested against the following stable channels:
- Google Chrome 124
- Microsoft Edge 124
-
Method [
method: BrowserContext.clearCookies
] now supports filters to remove only some cookies.// Clear all cookies. await Context.ClearCookiesAsync(); // New: clear cookies with a particular name. await Context.ClearCookiesAsync(new() { Name = "session-id" }); // New: clear cookies for a particular domain. await Context.ClearCookiesAsync(new() { Domain = "my-origin.com" });
-
New property [
method: Locator.contentFrame
] converts a [Locator] object to a [FrameLocator]. This can be useful when you have a [Locator] object obtained somewhere, and later on would like to interact with the content inside the frame.var locator = Page.Locator("iframe[name='embedded']"); // ... var frameLocator = locator.ContentFrame; await frameLocator.GetByRole(AriaRole.Button).ClickAsync();
-
New property [
method: FrameLocator.owner
] converts a [FrameLocator] object to a [Locator]. This can be useful when you have a [FrameLocator] object obtained somewhere, and later on would like to interact with theiframe
element.var frameLocator = page.FrameLocator("iframe[name='embedded']"); // ... var locator = frameLocator.Owner; await Expect(locator).ToBeVisibleAsync();
- Chromium 124.0.6367.8
- Mozilla Firefox 124.0
- WebKit 17.4
This version was also tested against the following stable channels:
- Google Chrome 123
- Microsoft Edge 123
New method [method: Page.addLocatorHandler
] registers a callback that will be invoked when specified element becomes visible and may block Playwright actions. The callback can get rid of the overlay. Here is an example that closes a cookie dialog when it appears.
// Setup the handler.
await Page.AddLocatorHandlerAsync(
Page.GetByRole(AriaRole.Heading, new() { Name = "Hej! You are in control of your cookies." }),
async () =>
{
await Page.GetByRole(AriaRole.Button, new() { Name = "Accept all" }).ClickAsync();
});
// Write the test as usual.
await Page.GotoAsync("https://www.ikea.com/");
await Page.GetByRole(AriaRole.Link, new() { Name = "Collection of blue and white" }).ClickAsync();
await Expect(Page.GetByRole(AriaRole.Heading, new() { Name = "Light and easy" })).ToBeVisibleAsync();
- [
method: Page.pdf
] accepts two new options [option: Page.pdf.tagged
] and [option: Page.pdf.outline
].
⚠️ Ubuntu 18 is not supported anymore.
- Chromium 123.0.6312.4
- Mozilla Firefox 123.0
- WebKit 17.4
This version was also tested against the following stable channels:
- Google Chrome 122
- Microsoft Edge 123
- New method [
method: Page.unrouteAll
] removes all routes registered by [method: Page.route
] and [method: Page.routeFromHAR
]. Optionally allows to wait for ongoing routes to finish, or ignore any errors from them. - New method [
method: BrowserContext.unrouteAll
] removes all routes registered by [method: BrowserContext.route
] and [method: BrowserContext.routeFromHAR
]. Optionally allows to wait for ongoing routes to finish, or ignore any errors from them. - New options [
option: Page.screenshot.style
] in [method: Page.screenshot
] and [option: Locator.screenshot.style
] in [method: Locator.screenshot
] to add custom CSS to the page before taking a screenshot.
- Chromium 121.0.6167.57
- Mozilla Firefox 121.0
- WebKit 17.4
This version was also tested against the following stable channels:
- Google Chrome 120
- Microsoft Edge 120
New tools to generate assertions:
- "Assert visibility" tool generates [
method: LocatorAssertions.toBeVisible
]. - "Assert value" tool generates [
method: LocatorAssertions.toHaveValue
]. - "Assert text" tool generates [
method: LocatorAssertions.toContainText
].
Here is an example of a generated test with assertions:
await Page.GotoAsync("https://playwright.dev/");
await Page.GetByRole(AriaRole.Link, new() { Name = "Get started" }).ClickAsync();
await Expect(Page.GetByLabel("Breadcrumbs").GetByRole(AriaRole.List)).ToContainTextAsync("Installation");
await Expect(Page.GetByLabel("Search")).ToBeVisibleAsync();
await Page.GetByLabel("Search").ClickAsync();
await Page.GetByPlaceholder("Search docs").FillAsync("locator");
await Expect(Page.GetByPlaceholder("Search docs")).ToHaveValueAsync("locator");
- Options [
option: Page.close.reason
] in [method: Page.close
], [option: BrowserContext.close.reason
] in [method: BrowserContext.close
] and [option: Browser.close.reason
] in [method: Browser.close
]. Close reason is reported for all operations interrupted by the closure. - Option [
option: BrowserType.launchPersistentContext.firefoxUserPrefs
] in [method: BrowserType.launchPersistentContext
].
- Methods [
method: Download.path
] and [method: Download.createReadStream
] throw an error for failed and cancelled downloads. - Playwright docker image now comes with .NET 8 (new LTS).
- Chromium 120.0.6099.28
- Mozilla Firefox 119.0
- WebKit 17.4
This version was also tested against the following stable channels:
- Google Chrome 119
- Microsoft Edge 119
Evergreen browsers update.
- Chromium 119.0.6045.9
- Mozilla Firefox 118.0.1
- WebKit 17.4
This version was also tested against the following stable channels:
- Google Chrome 118
- Microsoft Edge 118
- Zoom into time range.
- Network panel redesign.
- [
event: BrowserContext.webError
] - [
method: Locator.pressSequentially
]
- The following methods were deprecated: [
method: Page.type
], [method: Frame.type
], [method: Locator.type
] and [method: ElementHandle.type
]. Please use [method: Locator.fill
] instead which is much faster. Use [method: Locator.pressSequentially
] only if there is a special keyboard handling on the page, and you need to press keys one-by-one.
- Chromium 117.0.5938.62
- Mozilla Firefox 117.0
- WebKit 17.0
This version was also tested against the following stable channels:
- Google Chrome 116
- Microsoft Edge 116
Playwright now supports Debian 12 Bookworm on both x86_64 and arm64 for Chromium, Firefox and WebKit. Let us know if you encounter any issues!
Linux support looks like this:
Ubuntu 20.04 | Ubuntu 22.04 | Debian 11 | Debian 12 | |
---|---|---|---|---|
Chromium | ✅ | ✅ | ✅ | ✅ |
WebKit | ✅ | ✅ | ✅ | ✅ |
Firefox | ✅ | ✅ | ✅ | ✅ |
- Chromium 116.0.5845.82
- Mozilla Firefox 115.0
- WebKit 17.0
This version was also tested against the following stable channels:
- Google Chrome 115
- Microsoft Edge 115
🏝️ Summer maintenance release.
- Chromium 115.0.5790.75
- Mozilla Firefox 115.0
- WebKit 17.0
This version was also tested against the following stable channels:
- Google Chrome 114
- Microsoft Edge 114
-
New option
MaskColor
for methods [method: Page.screenshot
] and [method: Locator.screenshot
] to change default masking color. -
New
uninstall
CLI command to uninstall browser binaries:$ pwsh bin/Debug/netX/playwright.ps1 uninstall # remove browsers installed by this installation $ pwsh bin/Debug/netX/playwright.ps1 uninstall --all # remove all ever-install Playwright browsers
- Chromium 115.0.5790.13
- Mozilla Firefox 113.0
- WebKit 16.4
This version was also tested against the following stable channels:
- Google Chrome 114
- Microsoft Edge 114
-
New [
method: Locator.and
] to create a locator that matches both locators.var button = page.GetByRole(AriaRole.BUTTON).And(page.GetByTitle("Subscribe"));
-
New events [
event: BrowserContext.console
] and [event: BrowserContext.dialog
] to subscribe to any dialogs and console messages from any page from the given browser context. Use the new methods [method: ConsoleMessage.page
] and [method: Dialog.page
] to pin-point event source.
- Chromium 114.0.5735.26
- Mozilla Firefox 113.0
- WebKit 16.4
This version was also tested against the following stable channels:
- Google Chrome 113
- Microsoft Edge 113
-
Use [
method: Locator.or
] to create a locator that matches either of the two locators. Consider a scenario where you'd like to click on a "New email" button, but sometimes a security settings dialog shows up instead. In this case, you can wait for either a "New email" button, or a dialog and act accordingly:var newEmail = Page.GetByRole(AriaRole.Button, new() { Name = "New email" }); var dialog = Page.GetByText("Confirm security settings"); await Expect(newEmail.Or(dialog)).ToBeVisibleAsync(); if (await dialog.IsVisibleAsync()) await Page.GetByRole(AriaRole.Button, new() { Name = "Dismiss" }).ClickAsync(); await newEmail.ClickAsync();
-
Use new options [
option: Locator.filter.hasNot
] and [option: Locator.filter.hasNotText
] in [method: Locator.filter
] to find elements that do not match certain conditions.var rowLocator = Page.Locator("tr"); await rowLocator .Filter(new() { HasNotText = "text in column 1" }) .Filter(new() { HasNot = Page.GetByRole(AriaRole.Button, new() { Name = "column 2 button" })}) .ScreenshotAsync();
-
Use new web-first assertion [
method: LocatorAssertions.toBeAttached
] to ensure that the element is present in the page's DOM. Do not confuse with the [method: LocatorAssertions.toBeVisible
] that ensures that element is both attached & visible.
- [
method: Locator.or
] - New option [
option: Locator.filter.hasNot
] in [method: Locator.filter
] - New option [
option: Locator.filter.hasNotText
] in [method: Locator.filter
] - [
method: LocatorAssertions.toBeAttached
] - New option [
option: Route.fetch.timeout
] in [method: Route.fetch
]
- The
mcr.microsoft.com/playwright/dotnet:v1.33.0
now serves a Playwright image based on Ubuntu Jammy. To use the focal-based image, please usemcr.microsoft.com/playwright/dotnet:v1.33.0-focal
instead.
- Chromium 113.0.5672.53
- Mozilla Firefox 112.0
- WebKit 16.4
This version was also tested against the following stable channels:
- Google Chrome 112
- Microsoft Edge 112
- New options [
option: Page.routeFromHAR.updateMode
] and [option: Page.routeFromHAR.updateContent
] in [method: Page.routeFromHAR
] and [method: BrowserContext.routeFromHAR
]. - Chaining existing locator objects, see locator docs for details.
- New option [
option: Tracing.startChunk.name
] in method [method: Tracing.startChunk
].
- Chromium 112.0.5615.29
- Mozilla Firefox 111.0
- WebKit 16.4
This version was also tested against the following stable channels:
- Google Chrome 111
- Microsoft Edge 111
-
New assertion [
method: LocatorAssertions.toBeInViewport
] ensures that locator points to an element that intersects viewport, according to the intersection observer API.var locator = Page.GetByRole(AriaRole.Button); // Make sure at least some part of element intersects viewport. await Expect(locator).ToBeInViewportAsync(); // Make sure element is fully outside of viewport. await Expect(locator).Not.ToBeInViewportAsync(); // Make sure that at least half of the element intersects viewport. await Expect(locator).ToBeInViewportAsync(new() { Ratio = 0.5 });
-
New methods [
method: BrowserContext.newCDPSession
] and [method: Browser.newBrowserCDPSession
] create a Chrome DevTools Protocol session for the page and browser respectively.
- DOM snapshots in trace viewer can be now opened in a separate window.
- New option [
option: Route.fetch.maxRedirects
] for method [method: Route.fetch
]. - Playwright now supports Debian 11 arm64.
- Official docker images now include Node 18 instead of Node 16.
- Chromium 111.0.5563.19
- Mozilla Firefox 109.0
- WebKit 16.4
This version was also tested against the following stable channels:
- Google Chrome 110
- Microsoft Edge 110
- Chromium 110.0.5481.38
- Mozilla Firefox 108.0.2
- WebKit 16.4
This version was also tested against the following stable channels:
- Google Chrome 109
- Microsoft Edge 109
-
New method [
method: Route.fetch
] and new optionJson
for [method: Route.fulfill
]:await Page.RouteAsync("**/api/settings", async route => { // Fetch original settings. var response = await route.FetchAsync(); // Force settings theme to a predefined value. var json = await response.JsonAsync<MyDataType>(); json.Theme = "Solarized"; // Fulfill with modified data. await route.FulfillAsync(new() { Json = json }); });
-
New method [
method: Locator.all
] to iterate over all matching elements:// Check all checkboxes! var checkboxes = Page.GetByRole(AriaRole.Checkbox); foreach (var checkbox in await checkboxes.AllAsync()) await checkbox.CheckAsync();
-
[
method: Locator.selectOption
] matches now by value or label:<select multiple> <option value="red">Red</option> <option value="green">Green</option> <option value="blue">Blue</option> </select>
await element.SelectOptionAsync("Red");
- Chromium 109.0.5414.46
- Mozilla Firefox 107.0
- WebKit 16.4
This version was also tested against the following stable channels:
- Google Chrome 108
- Microsoft Edge 108
- Live Locators in CodeGen. Generate a locator for any element on the page using "Explore" tool.
- [
method: Locator.blur
] - [
method: Locator.clear
]
- Chromium 108.0.5359.29
- Mozilla Firefox 106.0
- WebKit 16.4
This version was also tested against the following stable channels:
- Google Chrome 107
- Microsoft Edge 107
With these new APIs writing locators is a joy:
- [
method: Page.getByText
] to locate by text content. - [
method: Page.getByRole
] to locate by ARIA role, ARIA attributes and accessible name. - [
method: Page.getByLabel
] to locate a form control by associated label's text. - [
method: Page.getByTestId
] to locate an element based on itsdata-testid
attribute (other attribute can be configured). - [
method: Page.getByPlaceholder
] to locate an input by placeholder. - [
method: Page.getByAltText
] to locate an element, usually image, by its text alternative. - [
method: Page.getByTitle
] to locate an element by its title.
await page.GetByLabel("User Name").FillAsync("John");
await page.GetByLabel("Password").FillAsync("secret-password");
await page.GetByRole(AriaRole.Button, new() { NameString = "Sign in" }).ClickAsync();
await Expect(Page.GetByText("Welcome, John!")).ToBeVisibleAsync();
All the same methods are also available on [Locator], [FrameLocator] and [Frame] classes.
- As announced in v1.25, Ubuntu 18 will not be supported as of Dec 2022. In addition to that, there will be no WebKit updates on Ubuntu 18 starting from the next Playwright release.
-
[
method: LocatorAssertions.toHaveAttribute
] with an empty value does not match missing attribute anymore. For example, the following snippet will succeed whenbutton
does not have adisabled
attribute.await Expect(Page.GetByRole(AriaRole.Button)).ToHaveAttributeAsync("disabled", "");
- Chromium 107.0.5304.18
- Mozilla Firefox 105.0.1
- WebKit 16.0
This version was also tested against the following stable channels:
- Google Chrome 106
- Microsoft Edge 106
- New option
Enabled
for [method: LocatorAssertions.toBeEnabled
]. - [
method: LocatorAssertions.toHaveText
] now pierces open shadow roots. - New option
Editable
for [method: LocatorAssertions.toBeEditable
]. - New option
Visible
for [method: LocatorAssertions.toBeVisible
]. - [
method: APIResponseAssertions.toBeOK
] is now available.
- New option
MaxRedirects
for [method: APIRequestContext.get
] and others to limit redirect count. - Codegen now supports MSTest and NUnit frameworks.
- ASP .NET is now supported.
A bunch of Playwright APIs already support the WaitUntil: WaitUntilState.DOMContentLoaded
option.
For example:
await Page.GotoAsync("https://playwright.dev", new() { WaitUntil = WaitUntilState.DOMContentLoaded });
Prior to 1.26, this would wait for all iframes to fire the DOMContentLoaded
event.
To align with web specification, the WaitUntilState.DOMContentLoaded
value only waits for
the target frame to fire the 'DOMContentLoaded'
event. Use WaitUntil: WaitUntilState.Load
to wait for all iframes.
- Chromium 106.0.5249.30
- Mozilla Firefox 104.0
- WebKit 16.0
This version was also tested against the following stable channels:
- Google Chrome 105
- Microsoft Edge 105
Microsoft.Playwright.NUnit
and Microsoft.Playwright.MSTest
will now consider the .runsettings
file and passed settings via the CLI when running end-to-end tests. See in the documentation for a full list of supported settings.
The following does now work:
<?xml version="1.0" encoding="utf-8"?>
<RunSettings>
<!-- Playwright -->
<Playwright>
<BrowserName>chromium</BrowserName>
<ExpectTimeout>5000</ExpectTimeout>
<LaunchOptions>
<Headless>true</Headless>
<Channel>msedge</Channel>
</LaunchOptions>
</Playwright>
<!-- General run configuration -->
<RunConfiguration>
<EnvironmentVariables>
<!-- For debugging selectors, it's recommend to set the following environment variable -->
<DEBUG>pw:api</DEBUG>
</EnvironmentVariables>
</RunConfiguration>
</RunSettings>
- 🪦 This is the last release with macOS 10.15 support (deprecated as of 1.21).
⚠️ Ubuntu 18 is now deprecated and will not be supported as of Dec 2022.
- Chromium 105.0.5195.19
- Mozilla Firefox 103.0
- WebKit 16.0
This version was also tested against the following stable channels:
- Google Chrome 104
- Microsoft Edge 104
Playwright now supports Debian 11 Bullseye on x86_64 for Chromium, Firefox and WebKit. Let us know if you encounter any issues!
Linux support looks like this:
| | Ubuntu 20.04 | Ubuntu 22.04 | Debian 11 | :--- | :---: | :---: | :---: | :---: | | Chromium | ✅ | ✅ | ✅ | | WebKit | ✅ | ✅ | ✅ | | Firefox | ✅ | ✅ | ✅ |
We rewrote our Getting Started docs to be more end-to-end testing focused. Check them out on playwright.dev.
Playwright for .NET 1.23 introduces new API Testing that lets you send requests to the server directly from .NET! Now you can:
- test your server API
- prepare server side state before visiting the web application in a test
- validate server side post-conditions after running some actions in the browser
To do a request on behalf of Playwright's Page, use new [property: Page.request
] API:
// Do a GET request on behalf of page
var response = await Page.APIRequest.GetAsync("http://example.com/foo.json");
Console.WriteLine(response.Status);
Console.WriteLine(response.StatusText);
Console.WriteLine(response.Ok);
Console.WriteLine(response.Headers["Content-Type"]);
Console.WriteLine(await response.TextAsync());
Console.WriteLine((await response.JsonAsync())?.GetProperty("foo").GetString());
Read more about it in our API testing guide.
Now you can record network traffic into a HAR file and re-use this traffic in your tests.
To record network into HAR file:
pwsh bin/Debug/netX/playwright.ps1 open --save-har=example.har --save-har-glob="**/api/**" https://example.com
Alternatively, you can record HAR programmatically:
var context = await browser.NewContextAsync(new()
{
RecordHarPath = harPath,
RecordHarUrlFilterString = "**/api/**",
});
// ... Perform actions ...
// Close context to ensure HAR is saved to disk.
context.CloseAsync();
Use the new methods [method: Page.routeFromHAR
] or [method: BrowserContext.routeFromHAR
] to serve matching responses from the HAR file:
await context.RouteFromHARAsync("example.har");
Read more in our documentation.
You can now use [method: Route.fallback
] to defer routing to other handlers.
Consider the following example:
// Remove a header from all requests.
await page.RouteAsync("**/*", async route =>
{
var headers = route.Request.Headers;
headers.Remove("X-Secret");
await route.ContinueAsync(new() { Headers = headers });
});
// Abort all images.
await page.RouteAsync("**/*", async route =>
{
if (route.Request.ResourceType == "image")
{
await route.AbortAsync();
}
else
{
await route.FallbackAsync();
}
});
Note that the new methods [method: Page.routeFromHAR
] and [method: BrowserContext.routeFromHAR
] also participate in routing and could be deferred to.
- New method [
method: LocatorAssertions.toHaveValues
] that asserts all selected values of<select multiple>
element. - Methods [
method: LocatorAssertions.toContainText
] and [method: LocatorAssertions.toHaveText
] now acceptignoreCase
option.
- If there's a service worker that's in your way, you can now easily disable it with a new context option
serviceWorkers
:var context = await Browser.NewContextAsync(new() { ServiceWorkers = ServiceWorkerPolicy.Block });
- Using
.zip
path forrecordHar
context option automatically zips the resulting HAR:var context = await Browser.NewContextAsync(new() { RecordHarPath = "example.har.zip" });
- If you intend to edit HAR by hand, consider using the
"minimal"
HAR recording mode that only records information that is essential for replaying:var context = await Browser.NewContextAsync(new() { RecordHarPath = "example.har", RecordHarMode = HarMode.Minimal });
- Playwright now runs on Ubuntu 22 amd64 and Ubuntu 22 arm64.
- Playwright for .NET now supports linux-arm64 and provides a arm64 Ubuntu 20.04 Docker image for it.
-
Role selectors that allow selecting elements by their ARIA role, ARIA attributes and accessible name.
// Click a button with accessible name "log in" await page.Locator("role=button[name='log in']").ClickAsync();
Read more in our documentation.
-
New [
method: Locator.filter
] API to filter an existing locatorvar buttons = page.Locator("role=button"); // ... var submitLocator = buttons.Filter(new() { HasText = "Sign up" }); await submitLocator.ClickAsync();
-
New role selectors that allow selecting elements by their ARIA role, ARIA attributes and accessible name.
// Click a button with accessible name "log in" await page.Locator("role=button[name='log in']").ClickAsync();
Read more in our documentation.
-
New
scale
option in [method: Page.screenshot
] for smaller sized screenshots. -
New
caret
option in [method: Page.screenshot
] to control text caret. Defaults to"hide"
. -
We now ship a designated .NET docker image
mcr.microsoft.com/playwright/dotnet
. Read more in our documentation.
- Playwright now supports large file uploads (100s of MBs) via [
method: Locator.setInputFiles
] API.
- Chromium 101.0.4951.26
- Mozilla Firefox 98.0.2
- WebKit 15.4
This version was also tested against the following stable channels:
- Google Chrome 100
- Microsoft Edge 100
Playwright for .NET 1.20 introduces Web-First Assertions.
Consider the following example:
using System.Threading.Tasks;
using Microsoft.Playwright.NUnit;
using NUnit.Framework;
namespace PlaywrightTests;
[TestFixture]
public class ExampleTests : PageTest
{
[Test]
public async Task StatusBecomesSubmitted()
{
await Expect(Page.Locator(".status")).ToHaveTextAsync("Submitted");
}
}
Playwright will be re-testing the node with the selector .status
until
fetched Node has the "Submitted"
text. It will be re-fetching the node and
checking it over and over, until the condition is met or until the timeout is
reached. You can pass this timeout as an option.
Read more in our documentation.
- New options for methods [
method: Page.screenshot
], [method: Locator.screenshot
] and [method: ElementHandle.screenshot
]:- Option
ScreenshotAnimations.Disabled
rewinds all CSS animations and transitions to a consistent state - Option
mask: Locator[]
masks given elements, overlaying them with pink#FF00FF
boxes.
- Option
- [
method: Locator.highlight
] visually reveals element(s) for easier debugging.
- v1.20 is the last release to receive WebKit update for macOS 10.15 Catalina. Please update macOS to keep using latest & greatest WebKit!
- Chromium 101.0.4921.0
- Mozilla Firefox 97.0.1
- WebKit 15.4
This version was also tested against the following stable channels:
- Google Chrome 99
- Microsoft Edge 99
-
Locator now supports a
has
option that makes sure it contains another locator inside:await Page.Locator("article", new() { Has = Page.Locator(".highlight") }).ClickAsync();
Read more in locator documentation
-
New [
method: Locator.page
] -
[
method: Page.screenshot
] and [method: Locator.screenshot
] now automatically hide blinking caret -
Playwright Codegen now generates locators and frame locators
- Chromium 100.0.4863.0
- Mozilla Firefox 96.0.1
- WebKit 15.4
This version was also tested against the following stable channels:
- Google Chrome 98
- Microsoft Edge 98
- [
method: Locator.dragTo
] - Each locator can now be optionally filtered by the text it contains:
Read more in locator documentation
await Page.Locator("li", new() { HasTextString = "My Item" }) .Locator("button").click();
AcceptDownloads
option now defaults totrue
.Sources
option to embed sources into traces.
- Chromium 99.0.4812.0
- Mozilla Firefox 95.0
- WebKit 15.4
This version was also tested against the following stable channels:
- Google Chrome 97
- Microsoft Edge 97
Playwright 1.17 introduces frame locators - a locator to the iframe on the page. Frame locators capture the logic sufficient to retrieve the iframe
and then locate elements in that iframe. Frame locators are strict by default, will wait for iframe
to appear and can be used in Web-First assertions.
Frame locators can be created with either [method: Page.frameLocator
] or [method: Locator.frameLocator
] method.
var locator = page.FrameLocator("#my-frame").Locator("text=Submit");
await locator.ClickAsync();
Read more at our documentation.
Playwright Trace Viewer is now available online at https://trace.playwright.dev! Just drag-and-drop your trace.zip
file to inspect its contents.
NOTE: trace files are not uploaded anywhere; trace.playwright.dev is a progressive web application that processes traces locally.
- Playwright Test traces now include sources by default (these could be turned off with tracing option)
- Trace Viewer now shows test name
- New trace metadata tab with browser details
- Snapshots now have URL bar
- HTML report now supports dynamic filtering
- Report is now a single static HTML file that could be sent by e-mail or as a slack attachment.
- Playwright now supports Ubuntu 20.04 ARM64. You can now run Playwright tests inside Docker on Apple M1 and on Raspberry Pi.
- You can now use Playwright to install stable version of Edge on Linux:
pwsh bin/Debug/netX/playwright.ps1 install msedge
Wait for a locator to resolve to a single element with a given state.
Defaults to the state: 'visible'
.
var orderSent = page.Locator("#order-sent");
orderSent.WaitForAsync();
Read more about [method: Locator.waitFor
].
- run trace viewer with
pwsh bin/Debug/netX/playwright.ps1 show-trace
and drop trace files to the trace viewer PWA - better visual attribution of action targets
Read more about Trace Viewer.
- Chromium 97.0.4666.0
- Mozilla Firefox 93.0
- WebKit 15.4
This version of Playwright was also tested against the following stable channels:
- Google Chrome 94
- Microsoft Edge 94
By using [method: Mouse.wheel
] you are now able to scroll vertically or horizontally.
Previously it was not possible to get multiple header values of a response. This is now possible and additional helper functions are available:
- [
method: Request.allHeaders
] - [
method: Request.headersArray
] - [
method: Request.headerValue
] - [
method: Response.allHeaders
] - [
method: Response.headersArray
] - [
method: Response.headerValue
] - [
method: Response.headerValues
]
Its now possible to emulate the forced-colors
CSS media feature by passing it in the [method: Browser.newContext
] or calling [method: Page.emulateMedia
].
- [
method: Page.route
] accepts newtimes
option to specify how many times this route should be matched. - [
method: Page.setChecked
] and [method: Locator.setChecked
] were introduced to set the checked state of a checkbox. - [
method: Request.sizes
] Returns resource size information for given http request. - [
method: Tracing.startChunk
] - Start a new trace chunk. - [
method: Tracing.stopChunk
] - Stops a new trace chunk.
- ⬆ .NET Core Apps 2.1 are no longer supported for our CLI tooling. As of August 31st, 2021, .NET Core 2.1 is no longer supported and will not receive any security updates. We've decided to move the CLI forward and require .NET Core 3.1 as a minimum.
- Chromium 96.0.4641.0
- Mozilla Firefox 92.0
- WebKit 15.0
Selector ambiguity is a common problem in automation testing. "strict" mode ensures that your selector points to a single element and throws otherwise.
Set setStrict(true)
in your action calls to opt in.
// This will throw if you have more than one button!
await page.Locator("button", new() { Strict = true });
📍 New Locators API
Locator represents a view to the element(s) on the page. It captures the logic sufficient to retrieve the element at any given moment.
The difference between the Locator and ElementHandle is that the latter points to a particular element, while Locator captures the logic of how to retrieve that element.
Also, locators are "strict" by default!
var locator = page.Locator("button");
await locator.ClickAsync();
Learn more in the documentation.
React and Vue selectors allow selecting elements by its component name and/or property values. The syntax is very similar to attribute selectors and supports all attribute selector operators.
await page.Locator("_react=SubmitButton[enabled=true]").ClickAsync();
await page.Locator("_vue=submit-button[enabled=true]").ClickAsync();
Learn more in the react selectors documentation and the vue selectors documentation.
nth
selector engine is equivalent to the:nth-match
pseudo class, but could be combined with other selector engines.visible
selector engine is equivalent to the:visible
pseudo class, but could be combined with other selector engines.
// select the first button among all buttons
await button.ClickAsync("button >> nth=0");
// or if you are using locators, you can use First, Nth() and Last
await page.Locator("button").First.ClickAsync();
// click a visible button
await button.ClickAsync("button >> visible=true");
- Chromium 94.0.4595.0
- Mozilla Firefox 91.0
- WebKit 15.0
- 🖖 Programmatic drag-and-drop support via the [
method: Page.dragAndDrop
] API. - 🔎 Enhanced HAR with body sizes for requests and responses. Use via
recordHar
option in [method: Browser.newContext
].
- Playwright Trace Viewer now shows parameters, returned values and
console.log()
calls.
- Chromium 93.0.4576.0
- Mozilla Firefox 90.0
- WebKit 14.2
- new
baseURL
option in [method: Browser.newContext
] and [method: Browser.newPage
] - [
method: Response.securityDetails
] and [method: Response.serverAddr
] - [
method: Page.dragAndDrop
] and [method: Frame.dragAndDrop
] - [
method: Download.cancel
] - [
method: Page.inputValue
], [method: Frame.inputValue
] and [method: ElementHandle.inputValue
] - new
force
option in [method: Page.fill
], [method: Frame.fill
], and [method: ElementHandle.fill
] - new
force
option in [method: Page.selectOption
], [method: Frame.selectOption
], and [method: ElementHandle.selectOption
]
- Playwright for .NET v1.12 is now stable!
- Ships with the codegen and trace viewer tools out-of-the-box
- Chromium 93.0.4530.0
- Mozilla Firefox 89.0
- WebKit 14.2
This version of Playwright was also tested against the following stable channels:
- Google Chrome 91
- Microsoft Edge 91