This is an Appium 2.x plugin for AltUnity Tester.
- What is this for?
- Feature Overview
- Requirements and Assumptions
- Installation
- Reference
- The TypeScript AltUnity Client
- Contributing
The motivation behind this plugin is to make AltUnity Tester completely compatible with Appium, so that an Appium user doesn't need to learn the AltUnity API or download any extra clients or tools. In addition, it enables access to the excellent AltUnity Tester functionality while not being bound by the particular programming language requirements of that project (C# or Python).
The big idea behind AltUnity Tester in general is to allow for easier automation of Unity games, across all Unity platforms (mobile, desktop, etc...). While Appium already provides solid automation capabilities for UI-based apps, games tend to not use standard UI components and thus present themselves as a single opaque element to automation. AltUnity Tester is a Unity component you can include in your game that exposes a special websocket server from within the instrumented game. This allows for communication "into" the Unity context from the outside world, enabling inspecting of objects and triggering behaviours. The other half of AltUnity Tester is a set of client libraries used to speak to the WebSocket server more easily. These are written in Python and C#.
Many testers want to use both Appium and AltUnity, since Appium provides a lot of device automation features outside of what's happening in-game. Without this plugin, test authors needed to mix and match Appium and AltUnity API clients. With this plugin, test authors can stay entirely within the Appium scriptwriting paradigm and still take advantage of the power of AltUnity Tester.
- A new
UNITY
context, within which other functionality is made available - Get the 'page source' of the Unity game in XML format
- Find 'elements' (objects) via a number of strategies
- Interact with elements in basic ways (click/tap, get text, etc...)
- (Advanced) a TypeScript AltUnity Tester client (for use independently of the Appium plugin)
- You need a working Appium 2.0 server installation.
- You need existing Appium automation for the target platforms (e.g., if you want to automate a Unity game on Android, you need to already know how to automate Android apps with Appium in general, and have a functional setup).
- AltUnity Tester must be added to your Unity project, and you must have the instrumented version of the game.
- AltUnity Tester's WebSocket port must be accessible to Appium. This means, for example, that you
will need to set up any necessary port forwarding.
-
Example: if the AltUnity Tester port is
13000
, and you're running on an Android device, you'll want to use ADB to forward the port to one on your system:adb forward tcp:13000 tcp:13000
-
Use the Appium plugin manager to install the most recent version of this plugin:
appium plugin install --source=npm appium-altunity-plugin
Then, when you start the Appium server, you need to ensure you have enabled the plugin for that
particular server instance, by including it in the list of plugins to use. The short name of this
plugin is altunity
:
appium --use-plugins=altunity
In terms of the client side of this plugin, no special installation is required as the plugin does not introduce any new commands, but rather makes use of existing Appium commands.
For a complete usage guide, check out the Reference Docs.
If you don't want to use the Appium plugin but are more interested in using AltUnity directly from TypeScript or JavaScript, you can also take advantage of the AltUnity client developed to enable this plugin. It is located in src/client and exports all types. You can import it in your own Node.js projects like this:
import { AltUnityClient } from 'appium-altunity-plugin'
This assumes that you have added this project to your package.json
, for example by:
npm install --save appium-altunity-plugin
Contributions to this plugin are welcome! It is developed under the Apache 2 license.
First, clone the repo:
git clone git@github.com:headspinio/appium-altunity-plugin.git
Then change into the repo dir and install dependencies:
npm install
Finally, transpile the project:
npm run build
It's always a good idea to run all tests before making any changes. First, get the sample app used in testing:
npm run pretest
Then, make sure Appium is using the local clone of this plugin (run from the plugin repo dir):
appium plugin uninstall altunity
appium plugin install --source=local $(pwd)
appium --use-plugins=altunity
Then ensure you have an Android emulator or device active and connected via ADB, that it is the only device showing in the device list, and that you have forwarded port 13000:
adb forward tcp:1300 tcp:1300
Finally, make sure adb
is available in your PATH. Now you're ready to run the tests!
npm run test:unit
npm run test:e2e
It's a good idea to set things up to automatically transpile any time you save a change to a file:
npm run watch
And remember that anytime you change and transpile the plugin, you'll need to stop and start the Appium server for the changes to take effect.