Other CI for mobile build testing

Upload mobile build artifacts and trigger test runs from any CI system without Node.js.

Use this guide if your CI system cannot run Node.js. This includes environments such as ArgoCD, locked-down runners, and minimal containers.

Make sure you have:

• A CI pipeline that produces a mobile build artifact (APK, AAB, or IPA).
• The ability to make HTTP requests from your CI environment (e.g. curl).
• Admin access to your CI system’s secret or environment variable storage.
• A QA Wolf API key.

Before mobile test runs can execute, QA Wolf must enable mobile triggers for your workspace. QA Wolf will handle this and may ask you for:

• Which environments you want to test.
• Whether PR testing is enabled.
• The artifact naming conventions you are using.

Until this step is complete, CI jobs can upload artifacts and send deployment notifications, but mobile test runs will not start automatically.

Find the QAWOLF_API_KEY

1. Open the Workspace name dropdown in QA Wolf and click Workspace Settings.

2. Choose Integrations.

3. Generate your QAWOLF_API_KEY by clicking the icon to the right of API Key under API Access.

Store the key as a secret in your CI system named QAWOLF_API_KEY.

Artifact naming conventions

Mobile build artifacts must follow consistent naming conventions so QA Wolf can correctly associate each build with the right environment.

Static environments

Format

<prefix>-<environment-name>

Example

app-staging

PR (ephemeral) environments

Format

<prefix>-<org>-<repo>-pr<number>

Example

app-myorg-myrepo-pr123

QA Wolf applies the file extension (.apk, .aab, or .ipa) automatically based on the uploaded artifact. You only need to provide the basename.

Upload the build artifact

Generate a signed URL

curl "https://app.qawolf.com/api/v0/run-inputs-executables-signed-urls?file=app-staging" \
  -H "Authorization: Bearer $QAWOLF_API_KEY"

On success, you’ll receive:

{
  "fileLocation": "$TEAM_ID/app-staging",
  "playgroundFileLocation": "app-staging",
  "signedUrl": "https://..."
}

Copy the playgroundFileLocation value — you’ll use it in the notify step.

Upload the file

curl -X PUT \
  --header "Content-Type: application/octet-stream" \
  --data-binary @./path/to/build.apk \
  "$SIGNED_URL"

Trigger a test run

After uploading the artifact, notify QA Wolf that a new deployment is ready for testing. Pass the playgroundFileLocation from the upload step as RUN_INPUT_PATH:

curl -X POST https://app.qawolf.com/api/webhooks/deploy_success \
  -H "Authorization: Bearer $QAWOLF_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "deployment_type": "staging",
    "variables": {
      "RUN_INPUT_PATH": "<playgroundFileLocation>"
    }
  }'

Replace deployment_type with the value your QA Wolf representative provides. Replace <playgroundFileLocation> with the value returned in the upload step.

A 200 response does not guarantee a run was created. Inspect the response body to confirm. See webhooks/deploy_success for full response details.

If mobile triggers have not yet been enabled, this step will complete without starting a test run.

Verify the integration

1. Run the CI job.

2. Verify that the artifact upload completes successfully.

3. Confirm that the deployment notification step runs without errors.

4. Once mobile triggers are enabled, check the Runs tab for the test run that was triggered.

Troubleshooting and common issues

• If uploads succeed but no runs start: Mobile triggers may not yet be enabled. Contact QA Wolf to complete platform configuration.
• If the artifact is not found during execution: Verify that the artifact basename matches your naming conventions, and that RUN_INPUT_PATH is set to the playgroundFileLocation value from the upload step.
• If you see authentication errors: Verify that QAWOLF_API_KEY is configured correctly in your CI environment.

Related

• webhooks/deploy_success
• v0/run-inputs-executables-signed-urls
• Other CI (Node)