Skip to main content

​
Overview: When to use the Fastlane integration

This guide is for teams that already use Fastlane to build Android or iOS apps. If your mobile builds are defined as Fastlane lanes, the QA Wolf Fastlane plugin lets you upload build artifacts and trigger test runs within your existing mobile automation. This is the recommended option for mobile teams that use Fastlane today. If you do not use Fastlane, use the QA Wolf CI SDK instead. QA Wolf does not set up Fastlane or create build lanes—this guide assumes Fastlane is already installed and producing a mobile build artifact.
Before configuring the Fastlane integration, make sure you have the following in place:
  • A working Fastlane setup for your Android or iOS app
  • A Fastlane lane that produces a mobile build artifact (APK, AAB, or IPA)
  • A QA Wolf API key stored as a secret in your CI environment
  • Artifact naming conventions are defined for your environments
Mobile triggers must be enabled for your workspace by QA Wolf before test runs will execute.
The Fastlane integration uses a QA Wolf Fastlane plugin to perform two actions:
1
Upload a mobile build artifact to QA Wolf
2
Notify QA Wolf of a deployment event so a test run can be triggered
You can upload builds without triggering runs, which is useful during initial setup or validation.The artifact name you provide is used to associate the build with the correct environment. QA Wolf automatically applies the file extension.
1
Add the QA Wolf Fastlane plugin to your project if it is not already installed. This is typically done in your Fastfile or plugin configuration, depending on how your project manages Fastlane plugins. Follow the instructions on the README to install.
2
Make sure your CI environment exports the QAWOLF_API_KEY environment variable so Fastlane can authenticate with QA Wolf.

​
To 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.
Once your Fastlane lane produces a build artifact, you can upload it to QA Wolf.
1
Add the upload_to_qawolf action to your lane and provide the artifact basename that matches your naming conventions. If this step completes successfully, the artifact has been uploaded and is available for use in test runs.

​
Example:

lane :qawolf do
  # Build your app
  gradle(
    task: "assemble",
    build_type: "Release"
  )

  # Upload the artifact to QA Wolf
  upload_to_qawolf(
    executable_file_basename: "app-staging"
  )
end
After uploading a build artifact, you can notify QA Wolf that a new deployment is ready for testing.
1
Add the notify_deploy_qawolf action to your lane. This step is optional and is required only if you want a test run to start automatically.
The environment key must match the value configured by QA Wolf for your workspace.
If mobile triggers have not yet been enabled, this step will complete without starting a test run.

​
Example:

notify_deploy_qawolf(
  executable_environment_key: "ANDROID_APP"
)
To verify the integration:
1
Run the Fastlane lane in CI.
2
Confirm the artifact upload step completes successfully.
3
Confirm the deploy notification step runs without errors.
4
Once mobile triggers are enabled, check the Runs tab to see the triggered test run.
If no run appears, the most common cause is a missing or incomplete QA Wolf platform configuration.
  • Artifact uploads succeed, but no runs start Mobile triggers may not be enabled yet. Contact QA Wolf to complete platform configuration.
  • Artifact not found during test execution Verify the artifact basename matches the expected naming conventions.
  • Authentication errors Confirm QAWOLF_API_KEY is set correctly in your CI environment.
  • Incorrect environment used Verify the environment key passed to notify_deploy_qawolf matches the configured value.
Last modified on February 9, 2026