Test Execution Best Practices

1 min read

Good execution practice keeps testing focused, repeatable, and useful for release decisions.

Choose the Right Workflow

Use Test Runs for standalone project testing such as regression, exploratory testing, smoke checks, or quick validation outside a release.

Use Release Executions when the testing belongs to a release milestone. A release can contain multiple executions, which helps teams compare initial testing, fix validation, regression, and final sign-off.

Learn more in Executions and Test Runs.

Keep Runs Focused

Create smaller runs or executions with a clear goal.
Select test cases manually, from requirements, or from test suites.
Avoid selecting every test case unless the goal is full regression.
Name executions clearly, such as v2.3 - Regression After Fixes.

Focused execution makes progress, ownership, and risk easier to understand.

Use Release Statuses Carefully

Release status controls whether release executions can continue:

Not Started: executions are allowed with a warning.
In Progress: executions are allowed.
Paused: execution is blocked until testing resumes.
Completed: execution changes are blocked.
Archived: the release is kept as read-only history.

Keep status current so the team knows whether testing is planned, active, paused, complete, or preserved for reference.

Learn more in Release Statuses.

Record Results Promptly

Use the visible result statuses consistently:

Passed
Failed
Blocked
Skipped
Not Executed

Add notes and attachments while the context is fresh. Use step-level notes when the issue belongs to a specific step.

Manage Ownership

Assign test cases to the people best placed to execute them.
Reassign work when availability changes.
Review unassigned and blocked test cases regularly.
Keep large executions from depending on one person.

Ownership keeps execution moving and makes follow-up clearer.

Close the Loop

After execution:

Review failed and blocked test cases.
Create or link defects for meaningful failures.
Re-run validation in a new execution when fixes are ready.
Use execution analysis and defect insights to decide what needs attention.

Execution is useful only when results drive action.