[Snyk] Upgrade playwright from 1.35.1 to 1.39.0

percona / percona-everest-cli

Apache License 2.0

6 stars 5 forks source link

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to upgrade playwright from 1.35.1 to 1.39.0.

:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

- The recommended version is **204 versions** ahead of your current version. - The recommended version was released **2 months ago**, on 2023-10-11.

Release notes

Package name: playwright

1.39.0 - 2023-10-11

Add custom matchers to your expect

You can extend Playwright assertions by providing custom matchers. These matchers will be available on the expect object.

import { expect as baseExpect } from '@ playwright/test';
export const expect = baseExpect.extend({
  async toHaveAmount(locator: Locator, expected: number, options?: { timeout?: number }) {
    // ... see documentation for how to write matchers.
  },
});

test('pass', async ({ page }) => {
  await expect(page.getByTestId('cart')).toHaveAmount(5);
});

See the documentation for a full example.

Merge test fixtures

You can now merge test fixtures from multiple files or modules:

import { mergeTests } from '@ playwright/test';
import { test as dbTest } from 'database-test-utils';
import { test as a11yTest } from 'a11y-test-utils';

export const test = mergeTests(dbTest, a11yTest);

import { test } from './fixtures';

test('passes', async ({ database, page, a11y }) => {
  // use database and a11y fixtures.
});

Merge custom expect matchers

You can now merge custom expect matchers from multiple files or modules:

import { mergeTests, mergeExpects } from '@ playwright/test';
import { test as dbTest, expect as dbExpect } from 'database-test-utils';
import { test as a11yTest, expect as a11yExpect } from 'a11y-test-utils';

export const test = mergeTests(dbTest, a11yTest);
export const expect = mergeExpects(dbExpect, a11yExpect);

import { test, expect } from './fixtures';

test('passes', async ({ page, database }) => {
  await expect(database).toHaveDatabaseUser('admin');
  await expect(page).toPassA11yAudit();
});

Hide implementation details: box test steps

You can mark a test.step() as "boxed" so that errors inside it point to the step call site.

async function login(page) {
  await test.step('login', async () => {
    // ...
  }, { box: true });  // Note the "box" option here.
}

Error: Timed out 5000ms waiting for expect(locator).toBeVisible()
  ... error details omitted ...

  14 |   await page.goto('https://github.com/login');
> 15 |   await login(page);
     |         ^
  16 | });

See test.step() documentation for a full example.

New APIs

expect(locator).toHaveAttribute(name)

Browser Versions

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

1.39.0-beta-1697610523000 - 2023-10-18
1.39.0-beta-1697575425000 - 2023-10-17
1.39.0-beta-1697093675000 - 2023-10-12
1.39.0-beta-1697057899000 - 2023-10-11
1.39.0-beta-1697048429000 - 2023-10-11
1.39.0-beta-1697047150000 - 2023-10-11
1.39.0-beta-1696976263000 - 2023-10-10
1.39.0-alpha-sep-30-2023 - 2023-09-30
1.39.0-alpha-sep-29-2023 - 2023-09-29
1.39.0-alpha-sep-28-2023 - 2023-09-28
1.39.0-alpha-sep-27-2023 - 2023-09-27
1.39.0-alpha-sep-26-2023 - 2023-09-26
1.39.0-alpha-sep-25-2023 - 2023-09-25
1.39.0-alpha-sep-24-2023 - 2023-09-24
1.39.0-alpha-sep-23-2023 - 2023-09-23
1.39.0-alpha-sep-22-2023 - 2023-09-22
1.39.0-alpha-sep-21-2023 - 2023-09-21
1.39.0-alpha-sep-20-2023 - 2023-09-20
1.39.0-alpha-sep-19-2023 - 2023-09-19
1.39.0-alpha-sep-18-2023 - 2023-09-18
1.39.0-alpha-sep-17-2023 - 2023-09-17
1.39.0-alpha-sep-16-2023 - 2023-09-16
1.39.0-alpha-sep-15-2023 - 2023-09-15
1.39.0-alpha-sep-14-2023 - 2023-09-14
1.39.0-alpha-sep-13-2023 - 2023-09-13
1.39.0-alpha-oct-9-2023 - 2023-10-09
1.39.0-alpha-oct-8-2023 - 2023-10-08
1.39.0-alpha-oct-7-2023 - 2023-10-07
1.39.0-alpha-oct-6-2023 - 2023-10-06
1.39.0-alpha-oct-5-2023 - 2023-10-05
1.39.0-alpha-oct-4-2023 - 2023-10-04
1.39.0-alpha-oct-3-2023 - 2023-10-03
1.39.0-alpha-oct-2-2023 - 2023-10-02
1.39.0-alpha-oct-10-2023 - 2023-10-10
1.39.0-alpha-oct-1-2023 - 2023-10-01
1.39.0-alpha-1696547902000 - 2023-10-05
1.39.0-alpha-1696536018000 - 2023-10-05
1.39.0-alpha-1694746830000 - 2023-09-15
1.38.1 - 2023-09-21
Highlights

#27071 - expect(value).toMatchSnapshot() deprecation announcement on V1.38
#27072 - [BUG] PWT trace viewer fails to load trace and throws TypeError
#27073 - [BUG] RangeError: Invalid time value
#27087 - [REGRESSION]: npx playwright test --list prints all tests twice
#27113 - [REGRESSION]: No longer able to extend PlaywrightTest.Matchers type for locators and pages
#27144 - [BUG]can not display trace
#27163 - [REGRESSION] Single Quote Wrongly Escaped by Locator When Using Unicode Flag
#27181 - [BUG] evaluate serializing fails at 1.38

Browser Versions
- 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
1.38.1-beta-1695325114000 - 2023-09-21
1.38.0 - 2023-09-13
UI Mode Updates
1. Zoom into time range.
2. Network panel redesign.
New APIs
- browserContext.on('weberror')
- locator.pressSequentially()
- The reporter.onEnd() now reports startTime and total run duration.
Deprecations
- The following methods were deprecated: page.type(), frame.type(), locator.type() and elementHandle.type().
  Please use locator.fill() instead which is much faster. Use locator.pressSequentially() only if there is a
  special keyboard handling on the page, and you need to press keys one-by-one.
Breaking Changes: Playwright no longer downloads browsers automatically

Note
If you are using @ playwright/test package, this change does not affect you.

Playwright recommends to use @ playwright/test package and download browsers via npx playwright install command. If you are following this recommendation, nothing has changed for you.

However, up to v1.38, installing the playwright package instead of @ playwright/test did automatically download browsers. This is no longer the case, and we recommend to explicitly download browsers via npx playwright install command.

v1.37 and earlier

playwright package was downloading browsers during npm install, while @ playwright/test was not.

v1.38 and later

playwright and @ playwright/test packages do not download browsers during npm install.

Recommended migration

Run npx playwright install to download browsers after npm install. For example, in your CI configuration:

<div class="highlight highlight-source-yaml notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="- run: npm ci
- run: npx playwright install --with-deps">
```
- run: npm ci
```
- run: npx playwright install --with-deps

Add @ playwright/browser-chromium, @ playwright/browser-firefox and @ playwright/browser-webkit as a dependency. These packages download respective browsers during npm install. Make sure you keep the version of all playwright packages in sync:

Browser Versions

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (07650d9) 5.33% compared to head (3e07007) 5.33%.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #225 +/- ## ===================================== Coverage 5.33% 5.33% ===================================== Files 13 13 Lines 2851 2851 ===================================== Hits 152 152 Misses 2672 2672 Partials 27 27 ```

percona / percona-everest-cli