A release check covers only pages changed directly

What to change

Choose regression coverage by dependency as well as by edited filename. Ask the supplier to identify which routes use the changed component and select representative important cases. Include a control path that should retain its behaviour. The owner need not inspect every implementation detail, but should see why the chosen sample is capable of detecting a shared failure. Preserve those examples with the component's change record for future releases.

A worked example

Illustrative example

Illustrative test: A shared navigation change is exercised from a guide, a service page and a directory.

How to check the result

The sample covers the dependency's real public reach.

A mistake to avoid

A file list can understate the impact of one reusable component.

Your action checklist

Use these checks to prepare a discussion with your team or supplier. Tick a check when you have recorded the decision or evidence, rather than when a feature has simply been promised.

Decisions to recordIdentify the public routes that depend on the changed component.Select representative actions across the affected template families.Repeat their agreed checks after the release.

Evidence, open questions and decisionsNext action and responsible role

Entries stay in this page and are not submitted to Kay & Co. Download your notes before leaving; the page does not save them.