Skip to content
certyn logoCertyn
Start Free
RecipesDoc

Plan Release 2.6.0 with Notes, a Target Date and Tests for What Changed

Declare the release, then get a test plan built from its notes and changelog, and run it on staging.

For QA leads who start a release and want the testing aimed at what changed.

Your setup

  • Your next version is 2.6.0, planned for 3 November.
  • You have release notes, or your deploy writes a changelog on the environment.
  • Staging runs the new version first. Certyn test cases cover parts of the app.
  • You want a short test plan, then the runs.

Say this to Certyn

Create release 2.6.0 for 2026-11-03 with these notes: bulk edit on /products, faster checkout, coupon rounding fix. Then plan tests for what changed and run them on staging once 2.6.0 is there.

What Certyn does

  1. Asks, then saves the release with its notes and target date (app.release.create). It names no environment yet: naming one sets that environment's version to 2.6.0 and starts its after-deploy processes.
  2. Reads what changed: your notes, and the changelogs of the last versions on staging (app.environment.get).
  3. Finds the test cases for each changed area by name, text or tag (app.find, app.testcase.list), and names the areas that have none.
  4. Proposes a plan: the matching test cases to run, and an explore run with a length for each area without tests, new features first.
  5. Checks the version on staging. When it is 2.6.0, it starts the runs after you agree (app.run.create type test_case with the ids, and type explore with minutes). If staging still runs an older version, it says so. Ask again after the deploy.

What you get

  • Release 2.6.0 on the Releases page, with notes and target date, and later its runs, issues and verdict.
  • A test plan tied to each change, with the gaps named.
  • Runs and issues saved against 2.6.0, ready for a go/no-go.

Limits

  • Certyn matches changes to test cases by their text, not by your code. A change it cannot match goes to an explore run. You can also name the test cases or a tag.
  • The chat sees only the first 300 characters of each changelog. Paste long release notes into your message.
  • A run belongs to 2.6.0 only if staging runs 2.6.0 when the run starts. Set the version from your deploy.
  • Runs use plan time. Certyn says each run's length before it starts.
PreviousStripe Test Mode Payments and Feature Flags (LaunchDarkly or Similar)NextFollow One Version from Dev to Staging to Production