ADB over tcp stress testing

Why

Most teams looking to use STF as their IaaS provider for the devices they have in lab, have an implicit bias that "its not the same as a device connected via wired USB". Some of these concerns stem from the adb client being notoriously prone to disconnects and hence this creates a doubt of adding another layer might not be a good idea. This script can be used to stress test your setup to validate the stability of adb connection over remote/tcp and also vindicates the hardware choices recommended by OpenStf

What does it test

The script takes three arguments:

• The device serial no
• STF instance URL:port
• API token for auth

For every device you kick off this script, it downloads an open source app, and runs monkey stress test over the device while tailing the verbose output (which uses logcat) to local disk in a log file. This pretty much covers any device farm use case where you would want to constantly run test and tail logs.

Stress test script

https://gist.github.com/subash-canapathy/4d4c1ab7e07c7dcfc2989794a68cd4a9

What to look for

• Make sure the devices run the test completely (should be evident from the last log line)
• Additionally you can validate the hub's ability to keep the device charged even on constant test running over 8-10 hours.