component-driven / component-driven/cypress-axe
Question: What is the difference between cypress-axe and jest-axe?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 641
- Forks
- 90
- Avg merge
- 6h 8m
- Merged PRs (30d)
- 1
Description
Hi!
About cypress-axe and jest-axe
In terms of efficiency, their ability to detect A11Y errors, what is the difference between the two?
What are the things that one is not able to do but the other one is, for instance?
I am using a Design system on a website. In the website I would like implement cypress-axe testing, but the design system tests their component with jest-axe.
Would there be differences in what the two type of tests can detect? What I want to avoid I having cypress axe test failing because jest-axe was used and so Jest not being able to detect what cypress-axe will fail for.
Thanks!
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
No files, tests, or entry points are named. Compare the cypress-axe and jest-axe usage and their axe-core execution contexts, then document differences in coverage, efficiency, and limitations. Done means providing a clear comparison that explains whether Jest-based component tests leave Cypress-specific accessibility failures undetected.
Written by the indexing model from the issue text.
Assessment
- Domain
- accessibility, testing-qa
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100