chore(deps): update playwright to v1.44.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence	Type	Update
@playwright/test (source)	1.43.1 -> 1.44.0					devDependencies	minor
mcr.microsoft.com/playwright	v1.43.1 -> v1.44.0					final	minor

---

Release Notes

microsoft/playwright (@​playwright/test)

v1.44.0

Compare Source

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.

const locator = page.getByText('This interstitial covers the button');
await page.addLocatorHandler(locator, async overlay => {
  await overlay.locator('#close').click();
}, { times: 3, noWaitAfter: true });
// Run your tests that can be interrupted by the overlay.
// ...
await page.removeLocatorHandler(locator);

Miscellaneous options

• multipart option in apiRequestContext.fetch() now accepts FormData and supports repeating fields with the same name.

  const formData = new FormData();
  formData.append('file', new File(['let x = 2024;'], 'f1.js', { type: 'text/javascript' }));
  formData.append('file', new File(['hello'], 'f2.txt', { type: 'text/plain' }));
  context.request.post('https://example.com/uploadFiles', {
    multipart: formData
  });

• expect(callback).toPass({ intervals }) can now be configured by expect.toPass.inervals option globally in testConfig.expect or per project in testProject.expect.

• expect(page).toHaveURL(url) now supports ignoreCase option.

• testProject.ignoreSnapshots allows to configure per project whether to skip screenshot expectations.

Reporter API

• New method suite.entries() returns child test suites and test cases in their declaration order. suite.type and testCase.type can be used to tell apart test cases and suites in the list.
• Blob reporter now allows overriding report file path with a single option outputFile. The same option can also be specified as PLAYWRIGHT_BLOB_OUTPUT_FILE environment variable that might be more convenient on CI/CD.
• JUnit reporter now supports includeProjectInTestName option.

Command line

• --last-failed CLI option for running only tests that failed in the previous run.

  First run all tests:

  $ npx playwright test
  
  Running 103 tests using 5 workers
  ...
  2 failed
    [chromium] › my-test.spec.ts:8:5 › two ─────────────────────────────────────────────────────────
    [chromium] › my-test.spec.ts:13:5 › three ──────────────────────────────────────────────────────
  101 passed (30.0s)

  Now fix the failing tests and run Playwright again with --last-failed option:

  $ npx playwright test --last-failed
  
  Running 2 tests using 2 workers
    2 passed (1.2s)

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

---

Configuration

📅 Schedule: Branch creation - "every weekday before 11am" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
ionic-framework	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 17, 2024 8:36pm

[sean-perkins]

@thetaPC I wouldn't merge this as-is. The playwright version for the docker image should match the project dependency and renovate should be grouping those dependency updates:

ionic-framework/renovate.json5

Lines 24 to 40 in 88db938

	{
	matchDatasources: ["npm"],
	matchPackagePatterns: ["@playwright/test", "@axe-core/playwright"],
	groupName: "playwright",
	matchFileNames: [
	"core/package.json"
	]
	},
	{
	matchDatasources: ["docker"],
	matchPackageNames: ["mcr.microsoft.com/playwright"],
	groupName: "playwright",
	matchFileNames: [
	"core/Dockerfile"
	],
	versioning: "semver"
	},

I would have expected a bump to the lock file for the core package to @playwright/test.

[liamdebeasi]

This might have something to do with the age of the dependency. I ran into the same problem on a personal repo. Your renovatebot config requires a minimum release age of 3 days. This version of Playwright only came out yesterday, so the npm dependency has not met the min 3 day requirement.

I would have expected the same to be true for the Docker dependency, but maybe minimumReleaseAge works differently/is not supported with Docker deps?

[thetaPC]

I need to dig a bit deeper into this. Yesterday I was able to verify through the Renovate logs that it sees that Playwright needs to be updated. But it never commits to it. So the 3 day minimum mentioned by @liamdebeasi might not be related.

[thetaPC]

Based on my investigation, the renovate config needs to be modified. The current setup is allowing any package within the group to upgrade regardless if not all of them are ready. This GH discussions provides an example of how we should go about it. I'll open a separate PR to test it further.

In the meantime, Playwright finally updated after the 3 days minimum as mentioned so we can proceed.

The hold up is that some tests are failing. I was able to identify one of the issues is due to Playwright upgrading Chrome, which now has datetime acting differently when font size is scaling. This is actually good because now it behaves like the other browsers.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[thetaPC]

LGTM