-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
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
[BUG]: Intermittent ace.Checker is not a constructor errors in Jest tests #1025
Comments
Moving this issue into Triage pipeline to be prioritized to be looked at. |
I ran this boilerplate: https://github.com/IBMa/equal-access/tree/jest-puppeteer/accessibility-checker/boilerplates/jest-puppeteer-ts with 5 suites running 50 tests each using puppeteer and am not running into this. Are you sure you aren't sharing pages across tests and trying to load two tests into the same page at the same time? |
Triage meeting: |
Going to re-open this. Got some new reports. Will try again to reproduce this. |
Finally able to reproduce this on my end. Looking... |
Should be fixed in 3.1.44 |
Project
a11y checker
Browser
No response
Operating system
Other
Description
Hi there,
We import
accessibility-checker
into our node environment for use in Jest testing both locally and as part of our CI pipeline. We have begun seeing intermittent failures, usually all tests will pass without issue but occasionally the tests encounter errors:which leads to
in the same test.
When these errors occur often several tests still pass. All issues can be mitigated by using the Jest flag
--runInBand
forcing all tests to run sequentially although this is not ideal. This issue is highly reproducible on my 8 thread laptop.Steps to reproduce
I'll put together a reproducible repo if that would be helpful but I believe the steps are as follows
accessibility-checker
with Jest. Extend theexpect
functionality with theaccessibility-checker
compliance assertion.The text was updated successfully, but these errors were encountered: