Additional Testing for UiaTextRange #4421
Labels
Area-Accessibility
Issues related to accessibility
Area-CodeHealth
Issues related to code cleanliness, linting, rules, warnings, errors, static analysis, etc.
Issue-Task
It's a feature request, but it doesn't really need a major design.
Product-Terminal
The new Windows Terminal.
Milestone
Description of the new feature/enhancement
After #4018, more tests were added to UiaTextRange. However, there are still gaps in our testing and they require some more thought and additional refactoring. Here's some that I have in mind:
MoveByWord
MoveEndpointByUnitWord
FindText
GetBoundingRectangles
GetText
The word navigation tests are currently relying more on the tests within
TextBuffer
. So they might not need to be as cumbersome.FindText relies on our search module so that also isn't a high priority.
This is more of an opportunity to compare our accessibility model to others' and make sure we're not doing anything wonky (and preventing us from getting to that point).
These new tests also serve as a good opportunity to use
TEST_METHOD_PROPERTY
. Ideally, we could just have a standard set of tests across all text units and just iterate through those units.The text was updated successfully, but these errors were encountered: