I now recommend a user interface automation tool for a Windows-based WPF application in a company that targets a wide range of clients. The application runs at the WCF service level to receive data. The company already has a small VBScript infrastructure written specifically for Test Complete and is not really reliable, so I'm looking for a suitable tool where we could reuse scripts or Improve an existing tool. Any ideas are welcome.
I reviewed Microsoft UI Automation, Project White, UIA Verify, and Ranorex. Each of them has a lack of function.
I managed to go through the Microsoft UI Automation automation process. I am still in the process of understanding how this works with WPF, as it is completely dependent on IDS automation. Our application is huge and not written with this in mind. All code either does not implement the Automation identifier property or the Name property, which is very important for identifying an object in the visual tree in tools such as UISpy and VisualUIAVerify.
What I am considering in particular is the following. Please rate each of these
1) Recording: recording, playback and automatic execution of test scripts and report generation.
2) Dependencies: minimal dependencies (.NET platforms, API modules, SDK versions, etc.)
3)) Code generation: generating test script code from templates, macros and recordings.
4) Matching the name of the object. Avoid explicitly using IDS automation and screen cording if they use it, does it support any tools that will accept XAML files and insert automatic IDS into it, and also avoid problems with duplicate IDE automation.
5) Events: any events and callbacks that the user (tester) can receive if the graphical interface has undergone any changes and how the scripts will change in this case.
6) Support: support for different scripting languages and simple code conversion (C #, VBScript, Python, etc.)
7) Fast and reliable: simple and quick accessibility of GUI elements for manipulations (for example, support for xml dom, Json .. etc.), navigation, replacing duplicate code for changes in the user interface and simple configuration (xml, ini files)
8) Code converters: the tester writes the code in vbscript, and the developer can simply convert it to C # to embed them in any separate structure, if necessary).
9) Custom controls: support for custom controls and object mapping. If you have a custom object that behaves like one of the standard controls. can you match (tell the test tool that the user control behaves like a standard)? Does it support all standard control methods? Can you add your own control to your control class?
10) Reports. It should be possible to run several tests at once and create a report similar to VisualUIAVerify.