Test a feature and move it to Release

Checks run on the pull request. When they pass and the code is reviewed and merged, the card moves to Release.

In short

In Test, {{brand}} runs the feature's checks on the pull request, on the test copy. The checks are the new or changed ones the plan staged and the existing ones. When every check passes, the review is done and the pull request is merged, the card moves to Release.

Read the checks

1. Open the Feature card and its "Code & checks" tab. The checks are under the code.
2. Read "{passed} of {total} passed" and each check's result: "Passed", "Failed", "Running" or "Not run yet".
3. Look for "Staged" checks. They are new or changed, run on the pull request only, and merging applies them.

Result: failed checks are listed first, each with what it expected, what it got and when it ran.

Review and merge

1. Ask for the review if the board's "Code review" row is "1 person" or "2 people".
2. A reviewer presses "Approve the code review" on the card. It says "Your code review is recorded".
3. Merge the pull request in your repository, then look at "Staged" on the "Code & checks" tab.

Result: the card moves to Release, where it waits for its release to be shipped.

When a check fails

• The card turns red and says "A check failed" where it is. It does not move back by itself.
• Fix the code, or press "Send it back" to move the card to Develop.
• SQL checks have no preview, so they run after the merge.

Move a card without proof

1. Drag the card, or choose "Move to another stage" on its stage bar.
2. If the facts do not allow the move, the "Move without proof" box opens.
3. Choose "Move to", write "Why" and press "Move the card".

Result: the card carries "Moved without proof" with your reason. It is counted in the board's summary and report until the facts catch up. Moving backward needs no proof.

Good to know

• A manager can lock a gate. "The board locked this gate" means the card moves only when the facts prove it.
• Checks on the preview need a preview address on the environment of your tests. See /help/boards/coding-agent-on-a-card.
• "New checks needed before Release" can be "Existing checks only" when the feature needs none.
• What happens next: choose a release and release it. See /help/boards/releases-and-live.
• A change that touches payments, sign-in, personal data or the database needs two people's review and a written way back (how the team undoes the release in its own pipeline) before Release, whatever the preset. Someone who manages the board can lower the bar with a reason the card shows.
• A possible secret (a known key or token shape; the value is never shown) or a new package in the pull request is listed on the Code & checks tab. A person says they are fine, with a reason, before the card can go to Release.

If something goes wrong

• "Say why you are moving it." - the reason is required for a move forward without proof.
• "Waiting for the code review" - the checks passed and a review is still missing.
• "Waiting for a pull request" - the code is on the branch, but nothing is open.

Related

• /help/boards/build-a-feature
• /help/boards/releases-and-live
• /help/boards/how-a-feature-moves
• /help/boards/regression-check