TestPilot
TestPilot is RabbitQA's project-scoped manual test-management and execution workspace. It connects maintained test cases, Test Plans, Test Runs, execution results, issues, requirement-change impact, and quality reports for the selected RabbitQA project.
TestPilot is not the automated runner. Use AutoRunner for automated BDD execution and CI/CD workflows.
How the records fit together
| Record | Purpose |
|---|---|
| Test case | A maintained test definition stored in the shared Test Repository. |
| Test Plan | The broader quality objective that groups one or more Test Runs. |
| Test Run | One bounded execution cycle with dates, configuration, and assigned repository cases. |
| Test execution | The result-bearing instance created when a case is assigned to a Test Run. |
| Issue | A native RabbitQA issue or connected tracker item linked to testing evidence. |
Repository cases do not become executable merely because they exist. Assign them to a Test Run before working in Test Execution.
TestPilot areas
| Area | Use it to |
|---|---|
| Dashboard | Read plan, run, completion, pass-rate, trend, and recent-activity indicators. |
| Test Plans | Create and maintain the top-level quality groupings for execution cycles. |
| Test Runs | Configure a dated run and assign maintained repository cases. |
| Test Execution | Perform cases, save results and evidence, assign work, and review history. |
| Test Repository | Maintain the shared CaseWriter/TestPilot test-set and case hierarchy. |
| Impact Analyzer | Review how Analyzer document changes may affect regression coverage. |
| Issue Tracker | Search, create, link, export, and board native or connected issues. |
| Reports | Review and export the saved result state of a selected Test Run. |
Typical workflow
- Select the intended RabbitQA project.
- Create or verify maintained test cases in the Test Repository.
- Create a Test Plan for the quality objective.
- Create a Test Run under that plan and assign the exact cases to execute.
- Select the plan and run in Test Execution.
- Perform the steps, record observed outcomes, add evidence, and save the result.
- Create or link an issue when the evidence requires one.
- Review progress on the Dashboard and produce the selected run's report.
Example data in screenshots
The screenshots use a user-created ReleaseGuard plan, run, test set, and cases. These names illustrate the workflow; they are not built-in TestPilot content.
Important boundaries
- Pass rate is calculated from completed results; completion and progress include all assigned executions. A 100% pass rate can therefore coexist with incomplete coverage.
- Creating an issue and saving an execution result are separate actions.
- Jira and Azure board content requires the matching organization integration.
- Permissions can hide or disable create, edit, assignment, bulk-update, issue, and impact actions.
- The visible recurring Schedule controls on the current Test Run form do not yet persist a recurring schedule. Use Create Now for a run created from this screen.
Start with the Quick Start, or review Best Practices before planning a larger cycle.
