component-driven / component-driven/cypress-axe
checkA11y failing when called after setting cy.clock
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 641
- Forks
- 90
- Avg merge
- 6h 8m
- Merged PRs (30d)
- 1
Description
Hi,
I noticed that checkA11y failed when called after using the cy.clock(...) function to set a date
I get the following error when trying to call checkA11y :
cy.then() timed out after waiting 4000ms.
Your callback function returned a promise that never resolved.
The callback function was:
function(a){i(e)&&(e=void 0),i(t)&&(t=void 0),i(n)&&(n=void 0);var o=t||{},s=o.includedImpacts,u=r(o,["includedImpacts"]);return a.axe.run(e||a.document,u).then((function(e){var t=e.violations;return s&&Array.isArray(s)&&Boolean(s.length)?t.filter((function(e){return s.includes(e.impact)})):t}))}
Running cypress-axe 0.8.1 and cypress 4.12.1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure by calling cy.clock(...) before checkA11y with cypress-axe 0.8.1 and Cypress 4.12.1, then trace the promise shown in the timeout. The issue is done when checkA11y completes successfully after the clock is set and the relevant regression is covered by a test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cypress, typescript
- Domain
- accessibility, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100