How to mark feature tests with separate file for accessibility checks
What does this MR do and why?
We have hard time automating the test coverage for accessibility, because there's no rigid structure to them. Sometimes one view has multiple corresponding feature tests. We decided to opt for a separate file for accessibility checks for those scenarios.
Still, we need a way to determine the test coverage and monitor the progress of the Working Group efforts. I propose we mark feature tests that are covered in a separate file by a comment:
# covered by ./accessibility_spec.rbWe can then add it to our scanner rules to make the findings more accurate. This is of course prone to errors, we might need to occasionally add the comment where it was omitted. But it is by far the easiest way to solve our problems and allow us to start the actual work with the tests. We're blocked by this and I wasn't able to find another solution for it.
Let me know what you think
cc: @deepika.guliani @ramistry @ealcantara @sdejonge @rchanila
Related to Add a config to specify :wcag21aa as default le... (#421663) and specifically #421663 (comment 1518713768)
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
| Before | After |
|---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #420595