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
It's possible to intercept console errors in playwright. Let's update our test suite to detect console errors during runtime and fail if found.
Implementation here: https://github.com/microsoft/playwright/discussions/11690#discussioncomment-2060397
The text was updated successfully, but these errors were encountered:
npm run test:e2e:full runs without error
npm run test:e2e:full
Add the following to a test
wait page.evaluate(() => console.log('error'));
and verify that the test fails
Sorry, something went wrong.
Verified Fixed in Testathon on 06/27/22 by adding await page.evaluate(() => console.error('error')); to the smoke.e2e.spec.js test.
await page.evaluate(() => console.error('error'));
smoke.e2e.spec.js
Successfully merging a pull request may close this issue.
Summary
It's possible to intercept console errors in playwright. Let's update our test suite to detect console errors during runtime and fail if found.
Implementation here: https://github.com/microsoft/playwright/discussions/11690#discussioncomment-2060397
The text was updated successfully, but these errors were encountered: