Runtime issue: Axe is already running. Use `await axe.run()` to wait for the previous run to finish before starting a new run.
See original GitHub issue<< Please describe how you encountered this issue >>
axe-core version: undefined
axe-extension version: 4.24.5
it@moz-extension://a1c77a94-b956-419f-b37e-7d85e421f84d/axe-versions/latest/axe.js:12:78706
e/</axe.run@moz-extension://a1c77a94-b956-419f-b37e-7d85e421f84d/axe-versions/latest/axe.js:12:355675
48269/<@moz-extension://a1c77a94-b956-419f-b37e-7d85e421f84d/content.bundle.js:1:21730
async*72257/h</<@moz-extension://a1c77a94-b956-419f-b37e-7d85e421f84d/content.bundle.js:61:5845
Issue Analytics
- State:
- Created a year ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
How to use the axe-core.run function in axe-core - Snyk
it('should be accessible when a query triggers an error', async done => { // !BOOM addQueryFilter('$qre()'); buildErrortReportElement(); await afterQueryError ...
Read more >Axe API Documentation - Deque Systems
The axe API is designed to be an improvement over the previous generation of accessibility APIs. Click to explore the API's capabilities now....
Read more >Async/Await: subsequent awaits are not waiting for ones prior ...
Some of the functions being run take time to complete (upto 60 seconds). The problem is not the awaits seem to be waiting...
Read more >Asynchronous programming: futures, async, await | Dart
How using async and await affects execution order. ... Before running this example, try to spot the issue – what do you think...
Read more >@sa11y/jest - npm
Use await axe.run() to wait for the previous run to finish before starting a new run. try running tests serially by using Jest's...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Is there any solution for this issue when multiple tests are run concurrently? For example:
axe-core
(or a dependent likejest-axe
)Ran into this same problem; in my case the issue was that I’d wrapped
axe.run
in an async function, but forgotten to call that function withawait
in 2+ instances, which then clashed when run together.Commenting here in case others find this through Google like I did and happened to make the same mistake.