Skip to content

Include axe checks in todos feature test

What does this MR do and why?

Since there are 4 rspecs for todos dashboard, I decided to consolidate all scenarios for accessibility tests into one file, to save up on the test setup and have a clear picture which cases need to be covered with axe specs.

This follows our strategy: https://docs.gitlab.com/ee/development/fe_guide/accessibility/automated_testing.html#separate-file-for-extensive-test-suites

# covered by ./accessibility_spec.rb comment is needed for our semgrep scanner, that determines the accessibility test coverage.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After
Screenshot_2024-09-03_at_19.11.57 Screenshot_2024-09-03_at_18.46.04
Screenshot_2024-09-03_at_19.12.23 Screenshot_2024-09-03_at_19.08.21
Screenshot_2024-09-03_at_19.13.03 Screenshot_2024-09-03_at_19.18.47

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

Make sure the tests pass.

Related to #463584 (closed)

Edited by Paulina Sedlak-Jakubowska

Merge request reports

Loading