We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1.48.1
Given the following test:
test("non-breaking space bug", async ({ page }) => { await page.setContent(`<button>foo bar</button>`); await expect(page.getByRole("button", { name: "foo bar" })).toBeVisible(); await expect( page.getByRole("button", { name: "foo bar" }), ).toHaveAccessibleName("foo bar"); });
I expect the test to pass.
The test failed at expect.toHaveAccessibleName because:
expect.toHaveAccessibleName
Error: Timed out 5000ms waiting for expect(locator).toHaveAccessibleName(expected) Locator: getByRole('button', { name: 'foo bar' }) Expected string: "foo bar" Received string: "foo bar"
If you have console colors, there is a helpful highlight on the whitespace difference:
The HTML report doesn't have this feature.
No response
System: OS: macOS 15.1 CPU: (10) arm64 Apple M1 Pro Memory: 91.28 MB / 16.00 GB Binaries: Node: 20.17.0 - /opt/homebrew/opt/node@20/bin/node npm: 10.8.2 - /opt/homebrew/opt/node@20/bin/npm IDEs: VSCode: 1.94.0 - /usr/local/bin/code Languages: Bash: 3.2.57 - /bin/bash npmPackages: @playwright/test: ~1.48.1 => 1.48.1
The text was updated successfully, but these errors were encountered:
Potentially a duplicate of #23037.
Sorry, something went wrong.
HTML reporter was fixed to show where the diff is:
Is that in 1.48.2? I just installed it, but not getting a highlight in the HTML report:
Is that in 1.48.2?
Nope, that's @playwright/test@next, 1.49 that will release later this week.
Just verified, wonderful thank you. That helps mitigate this issue a bit.
dgozman
Successfully merging a pull request may close this issue.
Version
1.48.1
Steps to reproduce
Given the following test:
Expected behavior
I expect the test to pass.
Actual behavior
The test failed at
expect.toHaveAccessibleName
because:If you have console colors, there is a helpful highlight on the whitespace difference:
The HTML report doesn't have this feature.
Additional context
No response
Environment
The text was updated successfully, but these errors were encountered: