add tests for symbol levels#13305
Merged
Merged
Conversation
"symbol level word" tests are disabled, expectations for these tests match the default symbol level tests to make change in behavior more obvious.
8 tasks
lukaszgo1
reviewed
Feb 3, 2022
This comment was marked as outdated.
This comment was marked as outdated.
Contributor
Author
|
We may want to add a test for symbols in table headers, see #12710 (comment) |
This comment was marked as outdated.
This comment was marked as outdated.
Contributor
Author
|
We may also want to add tests for selecting text by word, see #11779 (comment) |
seanbudd
previously approved these changes
Feb 8, 2022
seanbudd
left a comment
Member
There was a problem hiding this comment.
LGTM, do we have issues for the other test cases you want to cover? Or should they go in this PR?
Contributor
Author
These test symbols / pronunciation. Will need to introduce chrome for table tests.
Contributor
Author
|
I have added the extra test scenarios. |
seanbudd
reviewed
Feb 11, 2022
seanbudd
left a comment
Member
There was a problem hiding this comment.
LGTM other than the following addition. Due to the size of the PR, I plan to give it another read over just to see if anything else needs clarification.
lukaszgo1
reviewed
Feb 11, 2022
Demonstrate another silient word case, where multiple symbols make up a word (in notepad.exe). Expected behaviour unclear.
This comment was marked as outdated.
This comment was marked as outdated.
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Link to issue number:
Related to issue #11779, #10855, and PR #12710
Summary of the issue:
PR #12710 has been suffering from scope creep, several of the problems discussed pre-existed in NVDA.
With Symbol level all:
Description of how this pull request fixes the issue:
Note, this PR does not introduce user visible changes. It is intended to help developers reason about the behavior of NVDA.
Testing strategy:
System tests.
Known issues with pull request:
None
Change log entries:
None
Code Review Checklist: