Is your feature request related to a problem? Please describe.
We would like to use this tool in our desktop app automation tests, but we get many duplicates issues since we can only scan the entire app with the HWND. Our components do not have a specific HWND for each element.
Describe the solution you'd like
Instead of just taking the window handler, I would also like to be able to specify the child element I would want scanned by the automation ID or name.
Describe alternatives you've considered
We have considered scanning the entire page each time the automated test presses a button or moves to another part of the app, but this led to many duplicate issues. We also considered trying to add a HWND to each element.
Additional context
Example element to be scanned. This is selectable in Accessibility Insights for Windows and can be scanned by itself, however, doing this through the code is not possible.
Is your feature request related to a problem? Please describe.
We would like to use this tool in our desktop app automation tests, but we get many duplicates issues since we can only scan the entire app with the HWND. Our components do not have a specific HWND for each element.
Describe the solution you'd like
Instead of just taking the window handler, I would also like to be able to specify the child element I would want scanned by the automation ID or name.
Describe alternatives you've considered
We have considered scanning the entire page each time the automated test presses a button or moves to another part of the app, but this led to many duplicate issues. We also considered trying to add a HWND to each element.
Additional context
Example element to be scanned. This is selectable in Accessibility Insights for Windows and can be scanned by itself, however, doing this through the code is not possible.
