You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When doing UI Automation its often needed to retrieve the custom button or control status. E.g. a button is shown in blue or red or other specific status which depending on a certain status in the ViewModel cannot be reflected via standard properties like IsEnabled, IsClickable or button label etc.
Today via UI Testings this can only be checked/tested via screenshot tests (comparisions) which is not really maintenance friendly. Or provide custom renderers where custom status is set and provided on Android via AccessibilityNodeInfo.Text and on iOS via AccessibilityValue.
For UI Testing (E.g. Appium) but also for real Accessability use cases it would be extremly helpfull to provide in XF/MAUI an accessability status property which is bindable so that dynamic status information on a element can be set and provided to the user and UI Testing APIs.
The text was updated successfully, but these errors were encountered:
When doing UI Automation its often needed to retrieve the custom button or control status. E.g. a button is shown in blue or red or other specific status which depending on a certain status in the ViewModel cannot be reflected via standard properties like IsEnabled, IsClickable or button label etc.
Today via UI Testings this can only be checked/tested via screenshot tests (comparisions) which is not really maintenance friendly. Or provide custom renderers where custom status is set and provided on Android via AccessibilityNodeInfo.Text and on iOS via AccessibilityValue.
For UI Testing (E.g. Appium) but also for real Accessability use cases it would be extremly helpfull to provide in XF/MAUI an accessability status property which is bindable so that dynamic status information on a element can be set and provided to the user and UI Testing APIs.
The text was updated successfully, but these errors were encountered: