<aside> 📌 Available from CLI v1.12

</aside>

The goal is to run different user flows or steps in the app while measuring mobile performance KPIs. We can run these tests on real devices using Appium Java TestNG tests, while Apptim monitors the app.

How to run a TestNG test with Apptim?

Edit your test.yml and specify the test-file and the test-runner properties using the testng runner name. Optionally, Appium version can be set using the appium-version property, as follows:

test-file: ./test-with-dependencies.zip
test-runner:
	name: testng
  appium-version: '1.22.3'  # Change to install a custom appium version.
  node-version: '14.19.3'   # Optional if a custom node-version is needed.  

Then, to run the test use the command apptim run --config test.yml

How to configure testNG artifacts to work in AWS Device Farm?

A zip file containing your tests needs to be in a specific way in order to work out-of-the-box in AWS Device Farm. Read carefully this documentation to create your tests and zip file.

Important considerations:

• Do not add hardcoded capabilities to Appium, such as app file and device UDID. Those capabilities are set by default by AWS Device Farm when starting Appium.
• The zip file needs to have all you need (assets, config files, etc) to run independently of the source code. Be aware of relative paths when loading files.
• NodeJS installation takes a couple of minutes to complete, so don’t add a custom version unless strictly necessary.

Running Android tests with java 11

By default, the Android execution environment uses Java 8. If your tests use java 9 or higher, you need to add the following line in your test.yml file:

java-version: 11

Compatibility between Appium versions and iOS versions

• For iOS Devices on OS version 14.2 and above, please use Appium Version 1.19.0 or higher.