[Update 2023] AltUnity Pro Alpha is no longer available for download on our website. We are currently working on the launch of AltTester Pro, which will have support for WebGL and all the other features available in the AltUnity Pro Alpha.
[Update 2022] AltUnity Tester becomes AltTester Unity SDK starting with v. 1.8.0 and similarly, AltUnity Inspector becomes AltTester Desktop starting with v. 1.5.0 and they are both available here.
This comes with a series of major changes:
1. AltTester Unity SDK is now available only through our website and is no longer available on the Unity Asset Store
2. We moved the AltTester Unity SDK project from GitLab to GitHub.
Read more about all the major changes in this article and join our Discord Server, if you have any questions or issues with AltTester!
AltUnity Pro Alpha Overview
AltUnity Pro is a desktop application designed to make testing of Unity apps easier. It is designed to support WebGL and we plan on adding features like test report generation, integration with any popular cloud service and automatic test generation based on recorded actions. We also offer extended support and consultancy to help you with any difficulties you might encounter when using this app.
AltUnity Pro Alpha is the early version of AltUnity Pro and encapsulates some of the features of the final version. It offers support for WebGL on top of the features provided by AltUnity Tester and AltUnity Inspector. For those of you who are not familiar with AltUnity Tools, they make it possible to run tests on PC, Android and iOS. The main focus of AltUnity Pro Alpha is to address the community testing WebGL apps, to get feedback and continue developing a tool suitable for your needs.
How AltUnity Pro Alpha works
In order to test your application you need to create an instrumented build of your Unity App. The instrumented build opens a communication protocol which gives you programmatic access to objects inside your Unity App.
If you used AltUnity Tester before, there are two major changes you need to keep in mind.
Firstly, the communication between your tests and the instrumented Unity App is done via the AltUnity Connector, a proxy module that allows the game and the driver to communicate with each other. AltUnity Pro Alpha integrates the connector and your tests need to point to the IP address or hostname of the connector.
Secondly, the communication protocol between the driver and the instrumented game has changed radically since the 1.6.6 version release. You need the latest version of the driver to run your tests, that is any version >=1.7.0-alpha.
Components
AltUnity Tester Unity Package – tool for instrumenting your game.
AltUnity Driver (C#, Python, Java) – bindings for C#, Python and Java to write your tests.
AltUnity Pro Alpha – the AltUnity Connector that binds the drivers with the instrumented game, and AltUnity Inspector tool for interacting with the instrumented build and exploring the hierarchy of the unity objects.
Getting started
1. Get AltUnity Pro Alpha license and package
Send us an email to alttester@altom.com to get a free license for a period of 60 days and the necesary assets and packages.
2. Instrument your Unity application
To instrument your Unity application follow the guide from the documentation, using the Unity Package previously downloaded. Set the ProxyHost to the IP/hostname of the device where the AltUnity Pro Alpha is running. Set the ProxyPort to the port configured in the AltUnity Pro Alpha connection panel.
Note for existing AltUnity users: AltUnity Pro Alpha is not intended to work with Unity applications instrumented with the package downloaded from Unity Asset Store.
3. Connect your instrumented Unity app with AltUnity Pro Alpha
Start AltUnity Pro Alpha, review the listening port and click Start Connection. At this point the proxy is started and you can start the instrumented Unity app.
After the instrumented Unity app is connected to AltUnity Pro Alpha, you should get a view having 3 areas:
- area one containing screenshots of your app are displayed sequentially
- area two containing the hierarchy of your Unity objects
- area three containing the details of the selected hierarchy element.
4. Write and run your tests
After successfully instrumenting your game and connecting it with AltUnity Pro Alpha, it’s time to write and run your tests.
Before writing the tests make sure you have the latest alpha release of the driver libraries. You can follow the guide in the documentation to download the drivers and execute your first test.
Check out the API documentation for an overview of the available commands from AltUnity Tester.
5. Join our Discord server
We would be happy to get in touch with you trough our Discord Server, where you can offer feedback get support from us and other community members.
Example Project
If you’re just getting started with test automation for WebGL games, we have a test project which could help you. In this repository we use AltUnity Pro Alpha to write a few C# tests for a Unity Sample Game called “TANKS”. In the README file you’ll find instructions on how to run the tests.
Coming soon
We plan on making AltUnity Pro more complex by introducing features like:
Recording & Test Generation
This functionality allows you to record the actions taking place while testing. These actions will be translated into code so you don’t have to worry about writing the tests yourself.
Consoles
This feature will enable support for consoles.
Pipeline Support
This feature allows you to run your tests remotely on a runner.
Run Tests
Running tests on PC, iOS and Android will also be available in AltUnity Pro.
Your opinion matters!
We would be glad to receive your feedback on AltUnity Pro Alpha whether it is a new feature you would like to see in the future or a bug you found in our app. You can easily reach us to share your thoughts on Discord. If by any chance you encounter problems with the setup of AltUnity Pro Alpha you can address your issues on Discord as well in the altunity-pro-alpha channel.
It doesn’t support New Unity UI Builder. Is that something you are working on it?
We have looked into it and we are considering adding support for it, but we haven’t yet taken this into our pipeline. The more questions we get, the more we prioritise it though, so thanks for the comment!
Ru