Skip to content

Chore(deps): bump playwright from 1.35.0 to 1.45.1 in /pnpm

Bumps playwright from 1.35.0 to 1.45.1.

Release notes

Sourced from playwright's releases.

v1.45.1

Highlights

microsoft/playwright#31473 - [REGRESSION]: Playwright raises an error ENOENT: no such file or directory, open 'test-results/.playwright-artifacts-0/hash.zip' with Electron microsoft/playwright#31442 - [REGRESSION]: Locators of elements changing from/to hidden have operations hanging when using --disable-web-security microsoft/playwright#31431 - [REGRESSION]: NewTab doesn't work properly with Chrome with --disable-web-security microsoft/playwright#31425 - [REGRESSION]: beforeEach hooks are not skipped when describe condition depends on fixtures microsoft/playwright#31491 - [REGRESSION]: @playwright/experimental-ct-react doesn't work with VSCode extension and PNPM

Browser Versions

  • 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

v1.45.0

Clock

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 and let the page load naturally.
await page.clock.install({ time: new Date('2024-02-02T08:00:00') });
await page.goto('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.pauseAt(new Date('2024-02-02T10:00:00'));
// Assert the page state.
await expect(page.getByTestId('current-time')).toHaveText('2/2/2024, 10:00:00 AM');
// Close the laptop lid again and open it at 10:30am.
await page.clock.fastForward('30:00');
await expect(page.getByTestId('current-time')).toHaveText('2/2/2024, 10:30:00 AM');

See the clock guide for more details.

Test runner

  • New CLI option --fail-on-flaky-tests that sets exit code to 1 upon any flaky tests. Note that by default, the test runner exits with code 0 when all failed tests recovered upon a retry. With this option, the test run will fail in such case.

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by yurys, a new releaser for playwright since your current version.



Dependabot commands
You can trigger Dependabot actions by commenting on this MR
  • @dependabot-bot recreate will recreate this MR rewriting all the manual changes and resolving conflicts

Merge request reports