Currently, we offer two products:
Since those services are only supporting virtual devices, we recommend also recording your tests on the same virtual devices. Especially API level (=Android Version) and device architecture should match.
Even though Repeato CLI will run on pretty much any server, we currently offer 2 setup guides (more to come):
pushrule (any branch) can be used for workflow action to trigger (You may adjust according to your requirements).
Here is a demo workflow on Github actions that will help you get going:
macos-latestfor testing purposes. All steps will be performed on this machine.
Please make sure AVD or IOS emulator is ready and configured properly according to the workspace tests. You need to install your Android/ios app build on the emulator before this step. You must configure the AVD/IOS emulator with according to your local emulator on which you recorded Repeato tests. For iOS Simulator there isn’t any step, that starts the simulator, as the
xcodebuild test command for iOS Testing step boot’s the simulator by default.
The emulator needs some time to boot up. Place your step at the beginning of your workflow, so Bitrise will have more time to starting up the emulator while it takes car of other things, such as cloning or caching. We recommend that you also add Wait for Android emulator Bitrise Step (in case of android) to your Workflow as it acts as a shield preventing the AVD Manager to kick in too early. Make sure you add the Wait for Android emulator Step BEFORE the
Repeato CLI Step.
Here is our demo pipeline on Bitrise:
repeato-workspacewe are using: Same emulator settings as the once used for recording.
configuration sectionabove. This step will provide you with the ENV Variable
REPEATO_REPORTfor test batch reports. Use it for uploading the reports to your own or any 3rd party hosting service of your preference.
The final workflow should look similar to this: