Cypress: test for existance of 'cypress-a11y-report.json' before running 'yarn cypress-a11y-report' #7262
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR unblocks OLM queue!
It appears that our a11y reporting doesn't scale. A
cypress-a11y-report.json
is created in each package separately and the a11y script is only looking inpackages/integration-tests-cypress
. This PR checks for the existance ofpackages/integration-tests-cypress/cypress-a11y-report.json
first before executingyarn cypress-a11y-report
-so a11y results will only output forconsole
tests.A longer term solution is needed to figure out how to merge all the
cypress-a11y-report.json
files which maybe created in each package dir into a single json file. Should be straight forward as we already domochawesome-merge
for the cypress-unit json files.