26 / 26 Engineering and QA · Example
Review a release
The release review starts with a pass or fail for every critical path, walked through on staging.
- Who it’s for
- Release tools whose users walk the same few paths through staging by hand before every release.
- Why it’s hard
- The walk-through falls to whoever is free that afternoon, and gets shorter when they’re busy.
- You get back
-
- A pass or fail for every path, with its screenshot
- For each failure, the step where it broke
How it runs, in your product’s code
When 4.12 lands on staging, your product hands the computer the results from 4.11. Staging sits behind the company’s single sign-on, so an engineer signs in with their work account first. The computer then follows each path as written, from creating a Team workspace to cancelling the plan, and screenshots where each one ends. Any path that passed on 4.11 and fails now goes to the top of the report.