v1.27.0

Locators

With these new APIs, inspired by Testing Library, writing locators is a joy:

• page.getByText(text, options) to locate by text content.
• page.getByRole(role, options) to locate by ARIA role, ARIA attributes and accessible name.
• page.getByLabel(label, options) to locate a form control by associated label's text.
• page.getByPlaceholder(placeholder, options) to locate an input by placeholder.
• page.getByAltText(altText, options) to locate an element, usually image, by its text alternative.
• page.getByTitle(title, options) to locate an element by its title.

await page.getByLabel('User Name').fill('John');

await page.getByLabel('Password').fill('secret-password');

await page.getByRole('button', { name: 'Sign in' }).click();

await expect(page.getByText('Welcome, John!')).toBeVisible();

All the same methods are also available on Locator, FrameLocator and Frame classes.

Other highlights

• workers option in the playwright.config.ts now accepts a percentage string to use some of the available CPUs. You can also pass it in the command line:

  npx playwright test --workers=20%

• New options host and port for the html reporter.

  reporters: [['html', { host: 'localhost', port: '9223' }]]

• New field FullConfig.configFile is available to test reporters, specifying the path to the config file if any.

• 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.

Behavior Changes

• expect(locator).toHaveAttribute(name, value, options) with an empty value does not match missing attribute anymore. For example, the following snippet will succeed when button does not have a disabled attribute.

  await expect(page.getByRole('button')).toHaveAttribute('disabled', '');

• Command line options --grep and --grep-invert previously incorrectly ignored grep and grepInvert options specified in the config. Now all of them are applied together.

• JSON reporter path resolution is performed relative to the config directory instead of the current working directory:

  ["json", { outputFile: "./test-results/results.json" }]]

Browser Versions

• 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