This guide describes certain conventions we follow for testing mobile apps and using our tools to upload the build artifact and triggering test runs. Consider an in-depth version of Triggering test runs on deployment focused specifically on mobile apps.

Naming conventions

We expect the app filename to follow certain conventions to help identify and debug issues that may come up.

Static environment

Consider this your “Production” or “Staging” environment that is always present.

Format: <prefix>-<environment-name>.<extension>

Example: app-staging.apk

PR environment (ephemeral)

This is only relevant if you have completed Setting up PR Testing.

Format: <prefix>-<org>-<repo>-pr<number>.<extension>

Example: app-myorg-myrepo-pr123.apk

Initial app upload

This is typically done by the QA Wolf team. All we ask is that you provide a recent app file, whether it’s an APK, AAB, or IPA file.

CI/CD artifact upload and test triggers

To use these features, you will need to contact a QA Wolf representative to configure the trigger on the QA Wolf platform. On your end, you’ll need to decide what tool to use to upload the build artifact and trigger test runs. We support:

QA Wolf CI SDK example