Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider changing axe tests to run separate from e2e tests #16271

Open
mmalerba opened this issue Jun 11, 2019 · 3 comments
Open

Consider changing axe tests to run separate from e2e tests #16271

mmalerba opened this issue Jun 11, 2019 · 3 comments
Labels
Accessibility This issue is related to accessibility (a11y) area: dev-infra Issue related to internal project infrastructure feature This issue represents a new feature or feature request rather than a bug or bug fix P4 A relatively minor issue that is not relevant to core functions

Comments

@mmalerba
Copy link
Contributor

We should run axe tests on CI so we catch accessibility issues before running g3 presubmits

@mmalerba mmalerba added Accessibility This issue is related to accessibility (a11y) area: dev-infra Issue related to internal project infrastructure labels Jun 11, 2019
@josephperrott
Copy link
Member

Looks like we still run aXe tests on our e2e tests.

@jelbourn jelbourn changed the title Set up axe tests on CI Consider changing axe tests to run separate from e2e tests Jun 13, 2019
@jelbourn jelbourn added feature This issue represents a new feature or feature request rather than a bug or bug fix P4 A relatively minor issue that is not relevant to core functions labels Jun 13, 2019
@josephperrott josephperrott removed their assignment May 28, 2020
@angular-robot
Copy link
Contributor

angular-robot bot commented Feb 21, 2022

Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.

Find more details about Angular's feature request process in our documentation.

@angular-robot
Copy link
Contributor

angular-robot bot commented Mar 13, 2022

Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.

We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.

You can find more details about the feature request process in our documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Accessibility This issue is related to accessibility (a11y) area: dev-infra Issue related to internal project infrastructure feature This issue represents a new feature or feature request rather than a bug or bug fix P4 A relatively minor issue that is not relevant to core functions
Projects
None yet
Development

No branches or pull requests

4 participants