TestPilot Best Practices

Use these practices to keep test intent, execution scope, evidence, issues, progress, and reports consistent.

Plan the record hierarchy

• Use a Test Plan for the broader quality objective.
• Use a Test Run for one bounded, dated execution cycle.
• Keep reusable test intent in the shared Test Repository.
• Assign only the cases required for the current run.
• Use a separate run when dates, environment, scope, or quality decision differ materially.

Maintain executable cases

• Give each case a specific behavior-focused title.
• Keep prerequisites separate from actions.
• Make every expected result observable.
• Preserve a useful Test Set hierarchy for filtering and reporting.
• Edit maintained case content when test intent changes; do not hide a permanent correction only in an execution note.
• Review AI-generated or regenerated cases before saving or assigning them.

Record results from evidence

• Mark step outcomes from observed behavior.
• Choose an overall status that agrees with the steps.
• Write a Test Result Description that explains what was observed.
• Attach evidence when another reviewer cannot reproduce the decision from the text alone.
• Select Save Result and confirm the list state before relying on Dashboard or Reports.

Separate progress from pass rate

Pass rate considers completed results; progress and completion consider all assigned executions. Always report at least:

Signal	Question it answers
Completion	How much of the assigned scope has a saved result?
Result distribution	What states do the assigned cases currently have?
Pass rate	What portion of completed results Passed?
Issue coverage	Which observed failures or risks have traceable defects?

Keep result and issue persistence separate

• Save Result persists the execution.
• Create Issue persists a defect.
• Link Issue associates an existing connected record.

Complete every action the workflow requires. A Failed draft does not automatically create an issue, and a created issue does not automatically save the Failed result.

Use filters and bulk actions safely

• Confirm the selected Test Plan and Test Run first.
• Check active filters and the selected-row count before Apply Changes.
• Prefer a row action for one execution.
• Do not use presentation filters as a substitute for changing run scope.
• Use Manage Test Cases for assignment changes.

Respect current product boundaries

• Use Create Now in the current Test Run form. The visible Schedule controls do not yet persist a recurring schedule from that screen.
• Treat the current run Platform selection as a single stored choice and verify it after save.
• Jira and Azure boards, external issue sends, and Link Issue depend on organization connections.
• Impact Analyzer actions depend on role and processing availability.
• Hidden or disabled actions usually indicate a permission or integration boundary.

Protect retained evidence

• Read archive and delete confirmations completely.
• Archiving a plan removes it from the active list without treating it as deleted.
• The Test Plan delete confirmation states that linked runs are retained.
• Test Run deletion is described as irreversible.
• Before deleting, check reports, attachments, issue links, audit history, and downstream review needs.

Before a quality decision

1. Verify the selected project, plan, and run.
2. Reconcile report totals with the case table.
3. Review every Failed, Blocked, N/A, and Not Executed result.
4. Confirm the evidence and issue links.
5. Check completion separately from pass rate.
6. Export or share only after the saved state is correct.