Bump @playwright/test from 1.43.1 to 1.44.1
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-reportBrowser 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
noWaitAfteroption.- You can use new
timesoption 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
afacb84chore: mark v1.44.1 (#30942)be13365cherry-pick(#30853): chore: print friendly localhost address from http server...67b85e6docs: cherry-pick dotnet docs enhancements + release-notes (#30927)32bde52cherry-pick(#30832): chore(testServer): accept video parameter when running t...5d26230cherry-pick(#30807): chore: do not close the reused context when video is on3867d55cherry-pick(#30820): fix(electron): allow launching with spaces in path (#30830)01bf93ccherry-pick(#30800): Revert "fix(highlight): highlight Top Layer elements (#3...1b2de3fcherry-pick(#30708): docs(python): roll fixes (#30709)a6aa50bchore: set version to 1.44.0 (#30680)54c157dcherry-pick(#30677): chore: print resolved host in the http server te… (#30679)- Additional commits viewable in compare view
You can trigger a rebase of this PR by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.
will try and get to this soon.
@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
Preview URL :rocket: : https://blurts-server-pr-4585-mgjlpikfea-uk.a.run.app
A newer version of @playwright/test exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged.
@flozia any idea what's left on this one? Have we landed other @playwright/test updates in the meantime or are we stuck on this version?
@flozia any idea what's left on this one? Have we landed other
@playwright/testupdates in the meantime or are we stuck on this version?
@rhelmer We experienced test failures with 1.44.1 that we did not investigate further — upgrading to the latest version 1.46.1 with this PR now.
@dependabot merge
Cleanup completed - database 'blurts-server-pr-4585' destroyed, cloud run service 'blurts-server-pr-4585' destroyed