component-driven / component-driven/cypress-axe
consolidated a11y report
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 641
- Forks
- 90
- Avg merge
- 6h 8m
- Merged PRs (30d)
- 1
Description
I am using https://github.com/badeball/cypress-cucumber-preprocessor/
and have a data table with many pageUrls to test on, this feeds the test step, which results in separate test scenarios, all working fine and getting nice terminal outputs for each scenario.
How have you gone about obtaining a consolidated report for all scenarios / a11y checks?
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
The issue mentions cypress-cucumber-preprocessor, data tables, page URLs, scenarios, and accessibility checks, but names no repository files or tests. Start by reviewing the existing reporting guidance and determine whether consolidated output is documented; done means providing clear instructions for obtaining one report across all scenarios.
Written by the indexing model from the issue text.
Assessment
- Domain
- accessibility, testing-qa
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100