Skip to main content

Test the work

Test the complete change from its published branch. This stage is the implementer's automated and published-branch verification. It cannot be completed from uncommitted local work, and it does not replace human testing and acceptance criteria.

Published branch required

The source-code branch must be published. When the ticket includes Builder work, publish and select the corresponding Builder branch as well. Test the same artifacts that reviewers and testers will use.

Prerequisites​

  • A pull request linked to the ticket.
  • Access to the team's approved test environment. The environment URL and deploy steps are team-owned; this page does not name a single shared host.
  • The publish or import order recorded in the pull request's Builder section.

Prepare the test environment​

  1. Confirm the pull request points to the latest source-code commit.
  2. Open or deploy the published source-code branch in the approved test environment.
  3. Select or publish the Builder branch named in the pull request.
  4. Apply the publish or import order recorded on the pull request.
  5. Confirm the environment is using both intended branches before testing.

If a required branch cannot be selected or published, the work is blocked. Name the missing branch or access, assign an owner, and do not test a different artifact as a substitute.

Test checklist​

  • The source-code branch is published and contains the latest changes.
  • The required Builder branch is published and selected, or the pull request states that no Builder changes are required.
  • Automated checks associated with the published branch pass.
  • The expected behavior used during local execution still holds on the published branches.
  • Important error, permission, empty, loading, and boundary cases pass where relevant.
  • Existing behavior affected by the change has been checked for regression.
  • Test evidence and any limitations are recorded in the pull request.
  • The pull request is ready for human review and acceptance testing.

When testing fails​

Return to execution, correct the problem, and publish the updated source-code or Builder branch. Confirm the test environment has the new version, then repeat the affected tests. Do not send the change to human testing based on results from an earlier commit or Builder branch.

Expected result​

The published source-code and Builder branches pass automated checks and the implementer's branch tests. The pull request is ready for human testing against the ticket's acceptance criteria.

Next: Accept the work.