build: speed up docs deployment by not running a11y audit tests #24576
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We can speed up the docs deployment & monitor jobs by not running the rather slower a11y audit tests. These should just be run in the docs repo. The standard audit lighthouse tests should be a sufficient indicator of whether the page is up-and-running properly. Ideally in the future we would have proper e2e tests for the docs site, but even those will never guarantee a 100%-working page.
devversion
added
merge safe
target: patch
zarend
pushed a commit
that referenced
this pull request
Mar 14, 2022
We can speed up the docs deployment & monitor jobs by not running the rather slower a11y audit tests. These should just be run in the docs repo. The standard audit lighthouse tests should be a sufficient indicator of whether the page is up-and-running properly. Ideally in the future we would have proper e2e tests for the docs site, but even those will never guarantee a 100%-working page. (cherry picked from commit 5f864f1)
forsti0506
pushed a commit
to forsti0506/components
that referenced
this pull request
Apr 3, 2022
…lar#24576) We can speed up the docs deployment & monitor jobs by not running the rather slower a11y audit tests. These should just be run in the docs repo. The standard audit lighthouse tests should be a sufficient indicator of whether the page is up-and-running properly. Ideally in the future we would have proper e2e tests for the docs site, but even those will never guarantee a 100%-working page.
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
We can speed up the docs deployment & monitor jobs by not running the
rather slower a11y audit tests. These should just be run in the docs
repo. The standard audit lighthouse tests should be a sufficient
indicator of whether the page is up-and-running properly.
Ideally in the future we would have proper e2e tests for the docs
site, but even those will never guarantee a 100%-working page.