chore(deps): bump the playwright group across 1 directory with 3 updates

[dependabot]

Bumps the playwright group with 3 updates in the / directory: @playwright/test, playwright and playwright-core.

Updates @playwright/test from 1.40.1 to 1.45.0

Release notes

Sourced from @​playwright/test's releases.

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.

• New enviroment variable PLAYWRIGHT_FORCE_TTY controls whether built-in list, line and dot reporters assume a live terminal. For example, this could be useful to disable tty behavior when your CI environment does not handle ANSI control sequences well. Alternatively, you can enable tty behavior even when to live terminal is present, if you plan to post-process the output and handle control sequences.

  # Avoid TTY features that output ANSI control sequences
  PLAYWRIGHT_FORCE_TTY=0 npx playwright test
  Enable TTY features, assuming a terminal width 80
  PLAYWRIGHT_FORCE_TTY=80 npx playwright test

• New options testConfig.respectGitIgnore and testProject.respectGitIgnore control whether files matching .gitignore patterns are excluded when searching for tests.

• New property timeout is now available for custom expect matchers. This property takes into account playwright.config.ts and expect.configure().

  import { expect as baseExpect } from '@playwright/test';
  export const expect = baseExpect.extend({
  async toHaveAmount(locator: Locator, expected: number, options?: { timeout?: number }) {
  // When no timeout option is specified, use the config timeout.
  const timeout = options?.timeout ?? this.timeout;

... (truncated)

Commits

• 4f3f6ee cherry-pick(#31421): docs: release notes for 1.45
• d557b7b cherry-pick(#31420): docs(java): correctly parse time (#31422)
• 1368bca cherry-pick(#31419): docs: deprecate handle option in exposeBinding
• 6c3fc49 cherry-pick(#31404): feat(chromium): roll to r1124
• 4ae151f cherry-pick(#31340): docs: add guide for print dialogs
• a11585f cherry-pick(#31331): docs(test-parameterize): improve forEach example
• afcf8d2 cherry-pick(#31350): docs: fix typo in 1.45 release notes
• 599d074 cherry-pick(#31356): fix(clock): throw for invalid date
• 2451791 cherry-pick(#31357): fix(clock): under reused context
• 56ca1e1 cherry-pick(#31369): docs: use long for time in milliseconds (#31371)
• Additional commits viewable in compare view

Maintainer changes

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

Updates playwright from 1.40.1 to 1.45.0

Release notes

Sourced from playwright's releases.

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.

• New enviroment variable PLAYWRIGHT_FORCE_TTY controls whether built-in list, line and dot reporters assume a live terminal. For example, this could be useful to disable tty behavior when your CI environment does not handle ANSI control sequences well. Alternatively, you can enable tty behavior even when to live terminal is present, if you plan to post-process the output and handle control sequences.

  # Avoid TTY features that output ANSI control sequences
  PLAYWRIGHT_FORCE_TTY=0 npx playwright test
  Enable TTY features, assuming a terminal width 80
  PLAYWRIGHT_FORCE_TTY=80 npx playwright test

• New options testConfig.respectGitIgnore and testProject.respectGitIgnore control whether files matching .gitignore patterns are excluded when searching for tests.

• New property timeout is now available for custom expect matchers. This property takes into account playwright.config.ts and expect.configure().

  import { expect as baseExpect } from '@playwright/test';
  export const expect = baseExpect.extend({
  async toHaveAmount(locator: Locator, expected: number, options?: { timeout?: number }) {
  // When no timeout option is specified, use the config timeout.
  const timeout = options?.timeout ?? this.timeout;

... (truncated)

Commits

• 4f3f6ee cherry-pick(#31421): docs: release notes for 1.45
• d557b7b cherry-pick(#31420): docs(java): correctly parse time (#31422)
• 1368bca cherry-pick(#31419): docs: deprecate handle option in exposeBinding
• 6c3fc49 cherry-pick(#31404): feat(chromium): roll to r1124
• 4ae151f cherry-pick(#31340): docs: add guide for print dialogs
• a11585f cherry-pick(#31331): docs(test-parameterize): improve forEach example
• afcf8d2 cherry-pick(#31350): docs: fix typo in 1.45 release notes
• 599d074 cherry-pick(#31356): fix(clock): throw for invalid date
• 2451791 cherry-pick(#31357): fix(clock): under reused context
• 56ca1e1 cherry-pick(#31369): docs: use long for time in milliseconds (#31371)
• Additional commits viewable in compare view

Maintainer changes

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

Updates playwright-core from 1.40.1 to 1.45.0

Release notes

Sourced from playwright-core's releases.

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.

• New enviroment variable PLAYWRIGHT_FORCE_TTY controls whether built-in list, line and dot reporters assume a live terminal. For example, this could be useful to disable tty behavior when your CI environment does not handle ANSI control sequences well. Alternatively, you can enable tty behavior even when to live terminal is present, if you plan to post-process the output and handle control sequences.

  # Avoid TTY features that output ANSI control sequences
  PLAYWRIGHT_FORCE_TTY=0 npx playwright test
  Enable TTY features, assuming a terminal width 80
  PLAYWRIGHT_FORCE_TTY=80 npx playwright test

• New options testConfig.respectGitIgnore and testProject.respectGitIgnore control whether files matching .gitignore patterns are excluded when searching for tests.

• New property timeout is now available for custom expect matchers. This property takes into account playwright.config.ts and expect.configure().

  import { expect as baseExpect } from '@playwright/test';
  export const expect = baseExpect.extend({
  async toHaveAmount(locator: Locator, expected: number, options?: { timeout?: number }) {
  // When no timeout option is specified, use the config timeout.
  const timeout = options?.timeout ?? this.timeout;

... (truncated)

Commits

• 4f3f6ee cherry-pick(#31421): docs: release notes for 1.45
• d557b7b cherry-pick(#31420): docs(java): correctly parse time (#31422)
• 1368bca cherry-pick(#31419): docs: deprecate handle option in exposeBinding
• 6c3fc49 cherry-pick(#31404): feat(chromium): roll to r1124
• 4ae151f cherry-pick(#31340): docs: add guide for print dialogs
• a11585f cherry-pick(#31331): docs(test-parameterize): improve forEach example
• afcf8d2 cherry-pick(#31350): docs: fix typo in 1.45 release notes
• 599d074 cherry-pick(#31356): fix(clock): throw for invalid date
• 2451791 cherry-pick(#31357): fix(clock): under reused context
• 56ca1e1 cherry-pick(#31369): docs: use long for time in milliseconds (#31371)
• Additional commits viewable in compare view

Maintainer changes

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

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions