Bump @playwright/test from 1.43.1 to 1.44.1

[dependabot]

Bumps @playwright/test from 1.43.1 to 1.44.1.

Release notes

Sourced from @​playwright/test's releases.

v1.44.1

Highlights

microsoft/playwright#30779 - [REGRESSION]: When using video: 'on' with VSCode extension the browser got closed microsoft/playwright#30755 - [REGRESSION]: Electron launch with spaces inside executablePath didn't work microsoft/playwright#30770 - [REGRESSION]: Mask elements outside of viewport when creating fullscreen screenshots didn't work microsoft/playwright#30858 - [REGRESSION]: ipv6 got shown instead of localhost in show-trace/show-report

Browser Versions

• Chromium 125.0.6422.14
• Mozilla Firefox 125.0.1
• WebKit 17.4

This version was also tested against the following stable channels:

• Google Chrome 124
• Microsoft Edge 124

v1.44.0

New APIs

Accessibility assertions

• expect(locator).toHaveAccessibleName() checks if the element has the specified accessible name:

  const locator = page.getByRole('button');
  await expect(locator).toHaveAccessibleName('Submit');

• expect(locator).toHaveAccessibleDescription() checks if the element has the specified accessible description:

  const locator = page.getByRole('button');
  await expect(locator).toHaveAccessibleDescription('Upload a photo');

• expect(locator).toHaveRole() checks if the element has the specified ARIA role:

  const locator = page.getByTestId('save-button');
  await expect(locator).toHaveRole('button');

Locator handler

• After executing the handler added with page.addLocatorHandler(), Playwright will now wait until the overlay that triggered the handler is not visible anymore. You can opt-out of this behavior with the new noWaitAfter option.
• You can use new times option in page.addLocatorHandler() to specify maximum number of times the handler should be run.
• The handler in page.addLocatorHandler() now accepts the locator as argument.
• New page.removeLocatorHandler() method for removing previously added locator handlers.

... (truncated)

Commits

• afacb84 chore: mark v1.44.1 (#30942)
• be13365 cherry-pick(#30853): chore: print friendly localhost address from http server...
• 67b85e6 docs: cherry-pick dotnet docs enhancements + release-notes (#30927)
• 32bde52 cherry-pick(#30832): chore(testServer): accept video parameter when running t...
• 5d26230 cherry-pick(#30807): chore: do not close the reused context when video is on
• 3867d55 cherry-pick(#30820): fix(electron): allow launching with spaces in path (#30830)
• 01bf93c cherry-pick(#30800): Revert "fix(highlight): highlight Top Layer elements (#3...
• 1b2de3f cherry-pick(#30708): docs(python): roll fixes (#30709)
• a6aa50b chore: set version to 1.44.0 (#30680)
• 54c157d cherry-pick(#30677): chore: print resolved host in the http server te… (#30679)
• Additional commits viewable in compare view

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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[rafeerahman]

will try and get to this soon.

[rafeerahman]

@pdehaan Wondering if you could help look into this. For some reason the tests idle on the firefox browser with this version when sent to the subscription page.

After running npx playwright install, this test is an example of the idle state,

E2E_TEST_ENV="prod" npx playwright test -g "Verify that the user can select what type of plan they want" --project="firefox" --headed

See https://github.com/mozilla/blurts-server/actions/runs/9229668146 screenshots as well.

Relay firefox tests also fail on this 1.44.0, https://github.com/mozilla/fx-private-relay/actions/runs/9229683742/job/25396368649

[github-actions]

Preview URL 🚀 : https://blurts-server-pr-4585-mgjlpikfea-uk.a.run.app

[flozia]

@rafeerahman @mansaj It seems like there was an issue with determining the current Playwright version in CI. We should be able to just directly get it with npm view @playwright/test version.

[pdehaan]

@flozia I'm never sure when npm view queries the local package vs the remote registry. For example, this is what I see when running against main branch:

npm view @playwright/test version
# 1.44.1

npm ls @playwright/test
monitor@1.0.0 /Volumes/Dev/github/mozilla/blurts-server
├── @playwright/test@1.43.1
└─┬ next@14.2.3
  └── @playwright/test@1.43.1 deduped


npx playwright --version
# "Version 1.43.1"

Although, the playwright --version will return a string with the "Version " prefix, which might be ugly if we echo "Playwright Version: Version 1.44.1", so we might still need some sed magic:

npx playwright --version | sed 's/Version //'
# "1.43.1"

(since I'm very lazy and it's easier to remove the prefix than it is to try and match the semver string)

[flozia]

Yeah, that’s right: npm view might be a potential mismatch because it checks the remote version. Otherwise, npm ls @playwright/test --depth=0 | grep @playwright/test | sed 's/.*@//' could work as well. I like your suggestion to use npx since it is easy to parse — updated in a8bdde6.