v1.15.2

Highlights

This patch includes bug fixes for the following issues:

#9261 - [BUG] npm init playwright fails on path spaces
#9298 - [Question]: Should new Headers methods work in RouteAsync ?

Browser Versions

• Chromium 96.0.4641.0
• Mozilla Firefox 92.0
• WebKit 15.0

This version of Playwright was also tested against the following stable channels:

• Google Chrome 93
• Microsoft Edge 93

---

1.15.2-1633455481000

v1.15.1

Highlights

This patch includes bug fixes for the following issues:

#9065 - [BUG] browser(webkit): disable COOP support
#9092 - [BUG] browser(webkit): fix text padding
#9048 - [BUG] fix(test-runner): toHaveURL respect baseURL
#8955 - [BUG] fix(inspector): stop on all snapshottable actions
#8921 - [BUG] fix(test runner): after hooks step should not be nested
#8975 - [BUG] feat(fetch): support form data and json encodings
#9071 - [BUG] fix(fetch): be compatible with a 0 timeout
#8999 - [BUG] fix: do not dedup header values
#9038 - [BUG] fix: restore support for slowmo connect option

Browser Versions

• Chromium 96.0.4641.0
• Mozilla Firefox 92.0
• WebKit 15.0

This version of Playwright was also tested against the following stable channels:

• Google Chrome 93
• Microsoft Edge 93

---

1.15.0-1633020276000

v1.15.0

Playwright v1.15 updates

🎭 Playwright Library

🖱️ Mouse Wheel

By using Page.mouse.wheel you are now able to scroll vertically or horizontally.

📜 New Headers API

Previously it was not possible to get multiple header values of a response. This is now possible and additional helper functions are available:

• Request.allHeaders()
• Request.headersArray()
• Request.headerValue(name: string)
• Response.allHeaders()
• Response.headersArray()
• Response.headerValue(name: string)
• Response.headerValues(name: string)

🌈 Forced-Colors emulation

Its now possible to emulate the forced-colors CSS media feature by passing it in the context options or calling Page.emulateMedia().

New APIs

• Page.route() accepts new times option to specify how many times this route should be matched.
• Page.setChecked(selector: string, checked: boolean) and Locator.setChecked(selector: string, checked: boolean) was introduced to set the checked state of a checkbox.
• Request.sizes() Returns resource size information for given http request.
• BrowserContext.tracing.startChunk() - Start a new trace chunk.
• BrowserContext.tracing.stopChunk() - Stops a new trace chunk.

🎭 Playwright Test

🤝 test.parallel() run tests in the same file in parallel

test.describe.parallel('group', () => {
  test('runs in parallel 1', async ({ page }) => {
  });
  test('runs in parallel 2', async ({ page }) => {
  });
});

By default, tests in a single file are run in order. If you have many independent tests in a single file, you can now run them in parallel with test.describe.parallel(title, callback).

🛠 Add --debug CLI flag

By using npx playwright test --debug it will enable the Playwright Inspector for you to debug your tests.

Browser Versions

• Chromium 96.0.4641.0
• Mozilla Firefox 92.0
• WebKit 15.0

This version of Playwright was also tested against the following stable channels:

• Google Chrome 93
• Microsoft Edge 93

v1.14.1

Highlights

This patch includes bug fixes for the following issues:

#8287 - [BUG] webkit crashes intermittently: "file data stream has an unexpected number of bytes"
#8281 - [BUG] HTML report crashes if diff snapshot does not exists
#8230 - Using React Selectors with multiple React trees
#8366 - [BUG] Mark timeout in isVisible as deprecated and noop

Browser Versions

• Chromium 94.0.4595.0
• Mozilla Firefox 91.0
• WebKit 15.0

This version of Playwright was also tested against the following stable channels:

• Google Chrome 92
• Microsoft Edge 92

v1.14.0

Playwright v1.14 updates

🎭 Playwright Library

⚡️ New "strict" mode

Selector ambiguity is a common problem in automation testing. "strict" mode
ensures that your selector points to a single element and throws otherwise.

Pass strict: true into your action calls to opt in.

// This will throw if you have more than one button!
await page.click('button', { 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!

const locator = page.locator('button');
await locator.click();

Learn more in the documentation.

🧩 Experimental React and Vue selector engines

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.click('_react=SubmitButton[enabled=true]');
await page.click('_vue=submit-button[enabled=true]');

Learn more in the react selectors documentation and the vue selectors documentation.

✨ New nth and visible selector engines

• 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.click('button >> nth=0');
// or if you are using locators, you can use first(), nth() and last()
await page.locator('button').first().click();

// click a visible button
await button.click('button >> visible=true');

🎭 Playwright Test

✅ Web-First Assertions

expect now supports lots of new web-first assertions.

Consider the following example:

await expect(page.locator('.status')).toHaveText('Submitted');

Playwright Test 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 either pass this timeout or configure it once via the testProject.expect value in test config.

By default, the timeout for assertions is not set, so it'll wait forever, until the whole test times out.

List of all new assertions:

• expect(locator).toBeChecked()
• expect(locator).toBeDisabled()
• expect(locator).toBeEditable()
• expect(locator).toBeEmpty()
• expect(locator).toBeEnabled()
• expect(locator).toBeFocused()
• expect(locator).toBeHidden()
• expect(locator).toBeVisible()
• expect(locator).toContainText(text, options?)
• expect(locator).toHaveAttribute(name, value)
• expect(locator).toHaveClass(expected)
• expect(locator).toHaveCount(count)
• expect(locator).toHaveCSS(name, value)
• expect(locator).toHaveId(id)
• expect(locator).toHaveJSProperty(name, value)
• expect(locator).toHaveText(expected, options)
• expect(page).toHaveTitle(title)
• expect(page).toHaveURL(url)
• expect(locator).toHaveValue(value)

⛓ Serial mode with describe.serial

Declares a group of tests that should always be run serially. If one of the tests fails, all subsequent tests are skipped. All tests in a group are retried together.

test.describe.serial('group', () => {
  test('runs first', async ({ page }) => { /* ... */ });
  test('runs second', async ({ page }) => { /* ... */ });
});

Learn more in the documentation.

🐾 Steps API with test.step

Split long tests into multiple steps using test.step() API:

import { test, expect } from '@playwright/test';

test('test', async ({ page }) => {
  await test.step('Log in', async () => {
    // ...
  });
  await test.step('news feed', async () => {
    // ...
  });
});

Step information is exposed in reporters API.

🌎 Launch web server before running tests

To launch a server during the tests, use the webServer option in the configuration file. The server will wait for a given port to be available before running the tests, and the port will be passed over to Playwright as a baseURL when creating a context.

// playwright.config.ts
import { PlaywrightTestConfig } from '@playwright/test';
const config: PlaywrightTestConfig = {
  webServer: {
    command: 'npm run start', // command to launch
    port: 3000, // port to await for 
    timeout: 120 * 1000, 
    reuseExistingServer: !process.env.CI,
  },
};
export default config;

Learn more in the documentation.

Browser Versions

• Chromium 94.0.4595.0
• Mozilla Firefox 91.0
• WebKit 15.0

This version of Playwright was also tested against the following stable channels:

• Google Chrome 92
• Microsoft Edge 92

v1.13.1

Highlights

This patch includes bug fixes for the following issues:

#7800 - [Bug]: empty screen when opening trace.zip
#7785 - [Bug]: Channel installation requires curl/wget on the system
#7746 - [Bug]: global use is not working to launch firefox or webkit
#7849 - [Bug]: Setting the current shard through config uses n+1 instead

Browser Versions

• Chromium 93.0.4576.0
• Mozilla Firefox 90.0
• WebKit 14.2

v1.13.0

Playwright Test

• ⚡️ Introducing Reporter API which is already used to create an Allure Playwright reporter.
• ⛺️ New baseURL fixture to support relative paths in tests.

Playwright

• 🖖 Programmatic drag-and-drop support via the page.dragAndDrop() API.
• 🔎 Enhanced HAR with body sizes for requests and responses. Use via recordHar option in browser.newContext().

Tools

• Playwright Trace Viewer now shows parameters, returned values and console.log() calls.
• Playwright Inspector can generate Playwright Test tests.

New and Overhauled Guides

• Intro
• Authentication
• Chome Extensions
• Playwright Test Configuration
• Playwright Test Annotations
• Playwright Test Fixtures

Browser Versions

• Chromium 93.0.4576.0
• Mozilla Firefox 90.0
• WebKit 14.2

New Playwright APIs

• new baseURL option in browser.newContext() and browser.newPage()
• response.securityDetails() and response.serverAddr()
• page.dragAndDrop() and frame.dragAndDrop()
• download.cancel()
• page.inputValue(), frame.inputValue() and elementHandle.inputValue()
• new force option in page.fill(), frame.fill(), and elementHandle.fill()
• new force option in page.selectOption(), frame.selectOption(), and elementHandle.selectOption()

v1.12.3

Highlights

This patch release includes bug fixes for the following issues:

#7085 - [BUG] Traceviewer screens are not recorded well when using constructable stylesheets
#7093 - Folder for a test-case is getting generated in test-results even if Test Case Passes when properties are given on Failure
#7099 - [test-runner] Missing types for the expect library
#7124 - [Test Runner] config.outputDir must be an absolute path
#7141 - [Feature] Options for video resolution
#7163 - [Test runner] artifacts are removed
#7223 - [BUG] test-runner viewport can't be null
#7284 - [BUG] incorrect @playwright/test typings for toMatchSnapshot/toMatchInlineSnapshot/etc
#7304 - [BUG] Snapshots are not captured if there is an animation at the beginning
#7326 - [BUG] When PW timeouts, last trace action does not get collected[BUG] When PW timeouts, last trace action does not get collected

Browser Versions

• 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

v1.12.2

Highlights

This patch release includes bugfixes for the following issues:

• #7015 - [BUG] Firefox: strange undefined toJSON property on JS objects
• #7004 - [test runner] Error: Error while reading global-setup.ts: Cannot find module 'global-setup.ts'
• #7048 - [BUG] Dialogs cannot be dismissed if tracing is on in Chromium or Webkit
• #7058 - [BUG] Getting no video frame error for mobile chrome
• #7020 - [Feature] Codegen should be able to emit @playwright/test syntax

Browser Versions

• 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

v1.12.1

Highlights

This patch includes bug fixes for the following issues:

#6984 - slowMo does not exist in type 'Fixtures<{}, {}, PlaywrightTestOptions, PlaywrightWorkerOptions>'
#6982 - [trace viewer] srcset sanitization removes space between values, hence breaks the links
#6981 - [BUG] Getting "Please install @playwright/test package to use Playwright Test."

Browser Versions

• 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