Currently, automating the creation of FlaUI tests requires manually inspecting the UI structure to determine element IDs, AutomationIds, or other properties. This process can be tedious and prone to error.
Proposed Solution
I propose adding a feature that allows exporting the structure of a target UI element (and its descendants) into a JSON format.
This export function could be exposed on the AutomationElement class or through a new utility class. The JSON should capture key properties of each element in the tree, such as:
- ControlType (e.g., Button, TextBox)
- AutomationId
- Name
Currently, automating the creation of FlaUI tests requires manually inspecting the UI structure to determine element IDs, AutomationIds, or other properties. This process can be tedious and prone to error.
Proposed Solution
I propose adding a feature that allows exporting the structure of a target UI element (and its descendants) into a JSON format.
This export function could be exposed on the AutomationElement class or through a new utility class. The JSON should capture key properties of each element in the tree, such as: