`cy.then() timed out after waiting 4000ms. Your callback function returned a promise that never resolved.` on some tests using `axe-core` 4.7.1. about cypress-axe HOT 11 OPEN

@martinfer-newsuk It just started working on the project where I had the issue. Now i have the same issue on another project, so I guess i just have to wait until it resolves it self again :)

from cypress-axe.

I'm unable to find an issue within the page that's being scanned when we run into this problem. When I scan the page with the axe DevTools Chrome extension (axe-core version 4.7.1) no issues are identified. But, when I use cypress-axe with axe-core version 4.7.1 I get this time out error.

We're using Cypress 12.8.1 in Chrome 113 and cypress-axe 1.4.0, running on macOS 13.3.1 (a). We are trying to upgrade from axe-core version 4.4.2 (where we are not experiencing this problem) to version 4.7.1.

from cypress-axe.

@martinfer-newsuk Sadly, I have not been able to solve this.

from cypress-axe.

I just discovered that there are some scenarios this error occurs. Specifically a test where i waited for a named intercept. If i moved the cy.checkA11y() to the next test (which had the same rendered html), everything was fine. Just a tip.

from cypress-axe.

Thanks for the replies @frodehansen2 and @todd-m-kemp. The workaround of increasing the defaultCommandTimeout solved the errors we were having

from cypress-axe.

I only see this behaviour when the scan finds something wrong so far - I corrected an obvious issue on a new page and this error went away. I'm not sure what versioning is causing the difference in behaviour because we've recently done some upgrades to major dependencies across the board. We've been on the latest version of cypress-axe for awhile but we're now on Cypress v12.11.

from cypress-axe.

Any updates on this?

from cypress-axe.

@frodehansen2 @todd-m-kemp were you able to solve this? I've been running into this same issue 😞

from cypress-axe.

@todd-m-kemp guess I'll increase the defaultCommandTimeout on the test to avoid the error. Thanks for the response 🙏

from cypress-axe.

Thanks for the replies @frodehansen2 and @todd-m-kemp. The workaround of increasing the defaultCommandTimeout solved the errors we were having

That's good to hear! I just don't want to take that approach in our projects. 😂 Patiently awaiting a proper resolution here...

from cypress-axe.