Build regression coverage
Use this workflow when you want to check the same product behavior before releases or on a regular schedule. You will finish with a Test Plan containing cases you have already run and reviewed.
Before starting, create a project and prepare Test Accounts for authenticated journeys. If you have never run a case, follow the Quickstart first.
- ChoosePick a few journeys that would block a release.
- CreateGenerate, record, import, or write the cases.
- VerifyRun and review each workflow.
- GroupSave useful checks in a Test Plan.
1. Choose a small set of release checks
List the outcomes your team needs to trust. For a collaboration product, a first suite might include:
| Journey | Visible success condition |
|---|---|
| Sign in to the correct workspace | The workspace name and main navigation are visible. |
| Create a project or item | The new item appears in its list with the expected name. |
| Invite a teammate | The invitation appears with a pending status. |
| Check a restricted action | A member cannot access an administrator-only action. |
Make each case independent. Prepare the account, tenant, and data it needs instead of relying on another case to run first.
2. Create the cases
Choose the creation method that fits what you already have:
- Generate when the agent can explore the workflow from a focused scope.
- Record when showing the exact path is easier than describing it.
- Import when your existing instructions live in Excel.
- Write manually when you already know the actions and expected results.
Review generated drafts before clicking Create. Give each case an observable expected result and the correct Test Account. Use a folder such as Release smoke checks to keep the suite easy to manage.
3. Establish a useful first result
Run the saved cases in the background and review the results in Runs. If a case fails, inspect the evidence before changing the instructions or running it again.
Keep product failures visible. Correct instructions when they are stale, and prepare missing data or access when that prevented the check. Only treat a case as verified when its result supports the behavior it was meant to test.
4. Create a Test Plan
Open Test plans and click Create. Give it a recognizable name and choose Test scope. Use Select manually for an explicit first suite, or By folder for a maintained collection. Include Active cases with steps.
Leave Automatic runs off initially, save the plan, and run it manually. Review which cases actually executed and whether the result matches the suite you intended.
Check your progress
Your saved plan runs the intended Active cases, and your team knows where to inspect the result and its evidence.5. Choose when to repeat it
Once the suite is useful, enable Schedule for recurring checks or connect Webhook for testing after deployments. Add a notification rule so the team responsible for the workflow receives results.
Review coverage when the product changes. A plan resolves its scope again for each run, so edits to case status, priority, or folder membership can change what executes. See Test scope and automatic runs.