[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!
You use Unity’s Input System and now you wonder how you can easily write automated tests for your app? Or maybe you decided to use both Unity’s Input Manager and Input System and you are looking for a test automation framework that supports both? Whichever the case, this article is for you!
Support for Unity’s new Input System
AltUnity Tester v1.7.1 is here with support for Unity’s new Input System and the good news is that the commands’ interface remained unchanged. This means that, if you were using the previous version of AltUnity Tester, there is no need to make changes to your tests. All you have to do is import AltUnity Tester v.1.7.1 into your Unity project and follow these steps!
The commands that support both input systems are:
Besides the support for Input System, AltUnity Tester v1.7.1 comes with other new features.
As we love receiving feedback from the community using our tools, this command was implemented to solve an issue reported on Discord. MultipleKeyPress represents an extension of the KeyPress command.
Calling KeyPress multiple times consecutively would not have solved the problem of pressing more than one key within the same frame, as the keys given to these commands would trigger the key press in separate frames. However, using the MultipleKeyPress command you can now add a list of AltUnityKeyCodes to be pressed all in the same frame.
This command was inspired by the Proof of Concept we made for one of our clients – offering test automation services using our tools allows us to gain valuable feedback from these experiences. The need for the FindObjectAtCoordinates command came from the fact that we had to click on certain types of objects which would create different types of views.
As an example, by clicking on a street, a walk view similar to the one from Google Maps (street view) would be created, whereas clicking on a building would create a building view. Using this command gave us the ability to check whether or not we want to click on the object placed at specific coordinates or not.
In order to make the use of AltUnity Tester v.1.7.1 easier together with the Input System, we made a list of steps you have to follow to make sure you’ve got everything set up correctly. These steps include information on how to deal with Newtonsoft too, because we received a few questions on Discord related to this subject.
Check out the documentation, if you want to find more information about how to use AltUnity Tester!
Join our Discord community, if you need help, want to give feedback or need to ask any question related to our tools!
New Unity Test Automation Jumpstart Packages
We are now offering Unity test automation services for teams who want to get a solid Unity Testing framework. Through these packages, you’ll get access to a reliable test automation framework, interactive workshops and other customized services.
Find out more about our Unity Test Automation Jumpstart Packages from this link!