feat: Add jest shards in a11y tests #57
Merged
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.
Issue #, if available:
Description of changes:
Currently, the a11y tests takes around 30~35 minutes to be executed and it increases the waiting time for a PR to have a successful workflow action by almost 15 minutes as the highest tests that takes time after the a11y are the integ tests ( 15 mins )
This PR introduces jest shards, by which we divide the a11y into shards and each shard executes a subset of the tests in a separate machine. To create the shards mechanism we'll also have to merge the changes in the dry-run github workflow definition in this PR.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.