Add basic Android automated accessibility testing#11097
Closed
Conversation
hartez
force-pushed
the
automate-accessibility-testing
branch
from
fa45c2b to
283eaf4
Compare
hartez
force-pushed
the
automate-accessibility-testing
branch
from
283eaf4 to
9063f93
Compare
hartez
changed the title
Contributor
samhouts
added
stale
|
Hi @hartez. We have added the "s/pr-needs-author-input" label to this issue, which indicates that we have an open question/action for you before we can take further action. This PRwill be closed automatically in 14 days if we do not hear back from you by then - please feel free to re-open it if you come back to this PR after that time. |
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
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.
Description of Change
Add very basic automated accessibility testing for Android to Core device tests.
Keeping this a draft until #11021 is merged, will update it after that. This automation could also be applied to the Controls device tests, but again I want to wait until #11021 before tackling that and creating a ton of conflicts.