Skip to main content
Use this when a fastlane lane builds the iOS or Android binary for a pull request and you want a change review of that binary. To run a test plan against the build, use fastlane regression testing.

Set it up

Add the lane

Upload the pull request build, then start a change review pinned to it.

Post the review

Connect GitHub or GitLab so the agent can read the diff and post comments.

Get the results

Poll the conversation the same way as any other API-started review.
Store QATECH_API_TOKEN, QATECH_APP_ID, and, for org-scoped keys, QATECH_PROJECT_ID as described on fastlane regression testing. You do not need a test plan for a change review.

What works with fastlane

Add the lane

Copy qatech_request and qatech_upload_build from fastlane regression testing into fastlane/Fastfile, then add:
fastlane/Fastfile
For iOS, build and zip the simulator .app as in the regression lane, upload it with platform: "ios", then call qatech_change_review. Pass the pull request URL from your CI. On GitHub Actions:
Set PR_NUMBER from github.event.pull_request.number. For a GitLab merge request, pass the merge request URL and vcs_provider_id: "gitlab".

Post the review

fastlane does not post the review by itself. Before the lane calls the change review API:
  1. Connect the GitHub App with access to the repository, or connect GitLab MR reviews.
  2. Pass a pr_url the agent can resolve (GitHub PR or GitLab MR).
  3. The agent reads the diff and posts the review through that connection.
Without that connection, the conversation may start but nothing is posted on the request. Turn off GitHub App Auto-run on PRs when the lane owns the review, or a second review runs against the default environment instead of the PR build. Polling and dashboard links are the same as API pull request testing.