Pull request testing

Bring testing evidence to your pull request.

A pull request is where your team decides whether a change is ready to join the codebase. Bring the tested revision, recorded outcomes and outstanding questions into that review through an approved quality workflow.

Connect the repository and approve the scope.

GitHub inspection identifies an exact commit and supported repository configuration. Review the selected tests, intended target and bounded run cost before execution. Existing-test onboarding offers a small baseline, while a broader quality plan can include the additional methods your change needs. Repository access and current project permissions remain part of admission.

Make the evidence available where reviewers work.

The implemented GitHub integration can publish an App-owned evidence comment for an admitted PR run. It links to the protected report and retained artifacts, identifies the tested revisions and describes recorded outcomes. Required work without executable scope remains visible. Raw private test source stays in the protected evidence workflow rather than being copied into the discussion.

  • Review results for the exact tested head and base.
  • Follow the report link to inspect findings and artifacts.
  • See outstanding scope before treating a recommendation as ready.

Keep the recommendation current as the PR changes.

Changed source, plans or evidence can invalidate a previous recommendation. The integration rechecks PR state and updates its evidence comment through reconciliation. Your branch protection and human reviews remain authoritative. An evaluation confirms installation permissions, hosted execution and the desired workflow; a passing existing-test baseline alone cannot grant merge readiness.

Questions about this workflow

01Can new changes start testing automatically?

Configured watched changes can reuse explicitly approved standing intent when admission requirements are satisfied. Initial setup and changes to the relevant scope or authority still need review.

02Will the quality agent merge the pull request?

The evidence integration publishes testing information and a scoped recommendation. Repository rules and your authorised reviewers govern the merge decision.

Meet your AI testing workhorse

Bring your toughest code.
Set your highest bar.

See how the AI testing team would challenge your next release. We’ll scope the methods, automation and evidence around your software.

Request a walkthrough

Discuss an evaluation. No purchase commitment.