tarcv/testingteam-operator

Fork of Fork aiming at better JUnit compatibility and making development of UI tests less complex

Tongs

A kitchen tongs for distributing your candies across all the tasters/testers. It saves your time by running test cases in parallel on multiple devices simultaneously.

Tongs is based on Fork. It distributes execution of test cases across multiple devices making test runs much faster. And it provides valuable reports for them.

Differences from similar tools

• Full support for JUnit parameterized test cases - test case variants are distributed across devices
• Custom instrumentation runner arguments are supported, including filters
• Gradle support, including:
  • Support for split APKs
  • Install APKs with Gradle
• Tongs clears application data before test case execution
• Support for test frameworks other than JUnit 4 assuming their runners are compatible with AndroidJUnitRunner (see [Custom runners])

Running Tongs

Gradle plugin (recommended)

1. Add JitPack repository (this service builds packages directly from GitHub sources) and classpath plugin dependencies

buildscript {
  repositories {
    // other repos ...
    maven { url 'https://jitpack.io' }
  }
  dependencies {
    classpath 'com.github.TarCV:tongs:tongs-gradle-plugin:master-SNAPSHOT'
  }
}

2. Apply the plugin

apply plugin: 'com.github.tarcv.tongs'

3. Check tasks added by the plugin

./gradlew tasks | grep tongs

4. Run one of those tasks. For example:

./gradle tongs

Future plans

• Full support for JUnit assumptions
• Plugins
• Device flakiness reports

More docs soon

For now check repository of the project Tongs is based on.

testingteam-operator's Issues

Support APKs split by ABI in Gradle plugin

• Install/uninstall app with Gradle tasks
• Support testcases being executed only on some devices
• (if it's not too hard) Support JUnit assumptionsTurned out to be hard

Support JUnit assumptions

• Failed assumption should cause retry on a different device in the same pool
• Assumption failure should be reported as a skipped test for a particular device
• Test that has its assumptions failed on all devices in a pool should be reported as skipped

Properly reset device between tests

• Clean app data between tests
• Return to Home screen and close keyboard

DepShield Deprecation Notice

Depshield will be deprecated on Monday December 12th

Please install our new product, Sonatype Lift with advanced features

Prepare device before running tests

• Disable animations before tests
• Enable Keep awake with minimal brightness (if possible)
  Ideally the only thing you would have to prepare manually is disabling automatic lock
• Uninstall tested application before tests

Basic annotation support

• Read annotations
• GrantPermissions annotation
• Properties annotation