CI/CD Integration Document Integration for Travis CI

With just a few lines of script, you can enable along with Travis CI for out testbot to explore your apps and report results for every build process.

To use the service within Travis CI pipeline, you can take the following two steps: 1. Register the Access Key, and 2. add the to your build script (travis.yml)

Adding access key onto the build environment

  • Copy the access key string from the service profile page
  • Add access key to the build envirronment variable named APPTEST_AI_ACCESS_KEY and add the encryprion to the build script
$ travis login
$ travis encrypt APPTEST_AI_ACCESS_KEY="ID:Acess Key"  --add

The format for the access key becomes “ ID: Access Key“. For example, if the ID is and the access key is “ab8f3e321d631c84c9b1113”, the following applies:

After this command, the following “env:” section is added to the existing build script file. This section is replaced by the APPTEST_AI_ACCESS_KEY environment variable declaration at run time.

  - secure: fUnmuuqKmxWjxGHbfTB7QZgSmkB7yvt6KGAn8dCs1j4GneWbSIrEhghRrlOMQCThhMoetou4H+NaWeTXRRa4fpoCGm1U51RbD+J4DrbKWj3MzRupzByEAsaWhmvCaYVgCOlkYgaApcvujIrpw1rUTQVio8+WoYIXgXx3B
  • Now, add a script that executes the following after cloning the CI Tool integration script set by as follows.
- git clone
- export binary_path=HackerNews.ipa
- export project_id='825'
- bash ./ci_addon/

At least two arguments, binary_path and project_id, are required to invoke the service. binary_path is the path to the binary you want to test, i.e. * .apk files for android and * .ipa files for iOS. project_id is the Project ID for that contains the settings such as test time and device list for testing. The Project ID of can be found on the project information page as shown below.

If you don’t want to download’s CI integration script every time, include’s ci_addon repository in the Project Repository in advance.

  • Once you commit the build script, Travis CI will execute. When running script, the test is executed as shown below and the result is printed on the console.
  • The test results are stored in test-results/apptest-ai_result.html with detailed HTML report and an XML document in JUnit Test result format in test-results /apptestai/result.xml. You can save this file externally using various deploy functions provided by Travis CI. Below is an example of a release on Github. You can see the test report posted on Github’s release page.

If you want to change the location of the folder to store results, declare and pass test_result_path environment variable. If you want to execute the next build without waiting for the test to finish, declare waiting_for_test_results environment variable and pass FALSE.

Finally, here’s the .travis.yml example. First, for Android, in the “env” section, you can see that there are two secure environment variables for storing access key and two secure environment variables for Github acess key to deploy.

For an iOS case, iOS needs two more registered environment variables. This is an environment variable for code sign which is required when creating binary on iOS. Below we used a Fastlane match for the code sign. Fastlane match encrypts the certificate file and provisioning file required for code signing on Github, so two more access tokens and decryption keys are added to access a private GitHub repository where the certificate is stored compared to Android.