AltUnityTester Update – C# Editor Tests, More Actions and Java Bindings

[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!

Today we just released an update for AltUnityTester (v. 1.2), a Unity3d plugin that enabled UI automation on games and apps developed in Unity.

We described the reasoning behind AltUnityTester and our motivation in a longer blog post, here:

The first version of the plugin relied heavily on Appium for all interaction with elements, and AltUnityTester only provided the means to find Unity elements. In version 1.2, all that changes:

  • Appium is no longer required, but can be still used alongside AltUnityTester scripts to interact with the device
  • We have added C# support for writing tests, and you can now run these tests straight from the Unity Editor:
  • We added a lot of actions that can now be done straight from AltUnityTester, without the need to use Appium. For a full list, please see our docs here:
  • We added Java bindings – all actions are now supported from Java as well, these are available here

We plan to update the video tutorial soon to show how to use the new features. Until then, let us know how you find the new C# tests and using the Unity Editor!

Subscribe to our newsletter

And get our best articles in your inbox

 Back to top

5 responses to “AltUnityTester Update – C# Editor Tests, More Actions and Java Bindings

  1. This is a great tool! I love how easily it integrates with unity, and that tests can be written in C#. Thanks so much!

    Are there any forums to ask questions as development continues?

  2. v1.2 is really amazing. I had a confusion earlier that I thought I had to put the prefab in the scene like the old version, but the new version doesn’t need that. It is great, but I hope the next update can have a folder filter so it only shows the test created with it. For now it scans all the tests (unit test and all) in the Editor folders. And also, I had too guess what to put for calling object method and properties’ name. It turns out to be like this for example (“UnityEngine.UI.InputField”).
    Keep up the good work. This tool is really great!

    1. Thank you for the kind words, it’s great to know others find it useful!

      Your suggestions make a lot of sense and I will add them to the To Do list in Gitlab, they would definitely improve the user experience!

Leave a Reply

Your email address will not be published. Required fields are marked *