Sign in

Guide

A release review you can use on your next change.

Use these questions to turn a completion claim into a concrete acceptance decision. You can use this guide with or without Symbolic.

Get startedBook a demo
Illustrative workflow, not a live workspace result.
Claim
Profile changes are saved
Evidence
Reloaded value matches the edit
Environment
Named preview and revision
Unresolved
Expired-session recovery

What changes in your workflow

Passing a build is useful. It does not establish that the intended user can finish the task in the environment you plan to release.

Match the evidence to the claim

A page response supports reachability. A completed interaction supports that interaction. A value surviving reload supports persistence in the tested conditions.

Name the conditions

Record the revision, environment, user role, and relevant data state. A result from a preview or fixture should remain labeled that way.

Keep the gaps explicit

Separate failed, blocked, and untested work. State the next test or decision needed to resolve each item.

Put it into practice

  1. 01

    Read the acceptance criteria

    Can a reviewer tell exactly what the user should be able to do?

  2. 02

    Exercise the whole task

    Check the relevant starting state, action, result, and recovery path.

  3. 03

    Inspect the evidence

    Can another person identify what was observed and under which conditions?

  4. 04

    Make the decision

    Accept the supported scope or return the unresolved items with an owner and next step.

Explore the next step

Explore ChecksMap test coverageReview migration evidence

Give your next software change a clear acceptance test.

Start with a project, the behavior you need, and the evidence that would show it works.

Get startedBook a demo