At Last nights meeting Richard showed us a bit more of the UI
Testing that he has been using.
And how he uses the program FLAUInspect to find the various windows, buttons, components in the program under test. Which can then be used to automate it.
With some questions on testing firemonkey apps.
He showed a demo of a firemonkey Calculator he made, and how it doesn’t expose much of its window information to the world, though more/enough is shown if the Use Platform native option is chosen for the buttons.
My immediate thought was to create some sort of component you could drop on the main form, and connect to it externally, and it could iterate all the components and forms. However, this is only an option if you have the source to the program being tested.
Later overnight I had a thought that that you could perhaps create a DLL and inject it into the Program at runtime.
Here is a chatGPT session for FMX automation… haven’t had time to go much further, but it might be possible to assign an automation ID to the various components using Microsoft UI Automation and COM. It looks relatively complicated… So I would need to probably extend the ChatGPT session further.