Some years ago, my team at Altom started working on a few projects developing automated scripts for Unity apps. We were struggling to run UI driven tests on real devices. Looking for a solution, we started developing AltUnity Tester. This open-source asset helps game development teams find Unity objects and interact with them using C#, Java or Python tests. It allows running tests inside the Unity editor or on real devices (mobile, PC, etc.).
Recently we’ve extended AltUnity Tester with a desktop application, called AltUnity Inspector. It provides an easy way to visualize the object hierarchy, and get clear details of all the elements and properties needed for test automation. It also allows users to load different scenes of the game and interact with them using keyboard, mouse, touchscreen and joystick actions.
We are still surprised that many teams in the game development industry are not using automation. We know the process can be time-consuming and tedious, and we are trying to solve some of these problems through our tools. To achieve this, we need as much feedback as we can get.
We’d really like to hear about your thoughts regarding test automation for Unity apps. If you’ve already added test automation to your Unity development process, or thinking, it might help, try out our solution and let us know if it’s working for you.
Hi, and in advance: thanks for the effort your team is putting into the subject.
As a developer looking for automated ui-tests which can be integrated into a CI pipeline, I would like to know what framework is the right choice for our project.
From a glance at the surface, Unity Test Framework (About Unity Test Framework | Test Framework | 1.0.18) appears to address the same problem.
Could you highlight the differences between Unity Test Framework and AltUnity Tester?
I’d say the main difference is that the Unity Test Framework is suitable for unit and integration tests. Whereas AltUnity Tester is for end-to-end, UI test automation.
Some of the users from our community use both the Unity Test Framework and AltUnity Tools.
We have a new release! AltUnity Inspector 1.2 can now be downloaded!
We added some new features:
Objects hierarchy can be searched by every selector from AltUnity Tester (name, text, id, tag, layer, component, path). This allows you to validate your selectors before running tests.
Object path is displayed on the element details area. This can be copied directly to By.PATH method to quickly locate elements.
AltId, a unique object identifier generated by AltUnity Tester is also displayed and can be used with the By.ID selector.
Some of the new features are only supported by AltUnity Tester 1.6.4 and 1.6.3 so we recommend to use Inspector with an app instrumented with the latest version of AltUnity Tester.
Loading scenes both single and additive is now possible. Multiple scenes can be visualized both in the screenshot and objects hierarchy area.
The 5 latest connections are saved and users can choose from a list instead of introducing the IP and port numbers every time they connect a new device.
Other improvements:
refactored click, tap and press commands to make AltUnity Inspector more responsive.
fixed display issues related to fields and properties from the third column.
the hierarchy now remains scrolled into the expected view after scenes are changed or AltUnity Inspector is refreshed.
