In #923, we found that we set the bounds for accessibility wrong, which wasn't caught. I can see a few classes of tests which would help with this:
1) Tests which overlay all accessibility bounds on the app
2) Tests which use the accessibility bounds as the basis for e.g. a click/hover position, to make sure that the expected widget is clicked/hovered.
In #923, we found that we set the bounds for accessibility wrong, which wasn't caught. I can see a few classes of tests which would help with this: 1) Tests which overlay all accessibility bounds on the app 2) Tests which use the accessibility bounds as the basis for e.g. a click/hover position, to make sure that the expected widget is clicked/hovered.