TestPilot Module
TestPilot is RabbitQA's manual test management and execution workspace.
It is where you plan testing, organize it into runs, execute test cases by hand, record what happened, raise defects from failures, and report on the result.
How TestPilot is organized
TestPilot has three levels:
| Level | What it is |
|---|---|
| Test Plan | The top level. Groups related test runs for a release, sprint, or product area. |
| Test Run | A set of test cases executed together against one environment and one or more platforms. |
| Test Execution | One test case inside one run, with its own status, assignee, evidence, and linked issues. |
Test cases themselves live in the shared test repository, which CaseWriter owns. TestPilot reads from it and links to it rather than keeping its own copy.
Pages
| Page | What it is for |
|---|---|
| Dashboard | Workspace-level metrics, execution trends, active plans, and recent activity |
| Test Plans | Create plans and see the runs and health inside each one |
| Test Runs | Create, filter, and manage runs across plans |
| Test Executions | Execute tests and record results |
| Test Repository | The shared test case repository |
| Impact Analyzer | Turn document changes into suggested regression cases |
| Issue Tracker | Every issue raised from your executions, in one list |
| Reports | A detailed report per test run, with PDF and Excel export |
Opening /testpilot takes you to the dashboard.
What TestPilot tracks
Platforms
A run records which platforms it covers: WEB, MOBILE, API, or DESKTOP. A run can carry several at once, and the test case picker filters the repository accordingly.
TestPilot records the platform a test targets; it does not launch browsers, devices, or API clients itself.
Environments
DEVELOPMENT, TEST, STAGING, and PRODUCTION.
Run types
Regression, Smoke, Manual, and Automation.
Execution statuses
Passed, Bug Fixed, Running, Retest, Skipped, Blocked, Failed, N/A, and Not Executed.
Integrations
| Integration | What TestPilot does with it |
|---|---|
| Jira | Create, link, and browse issues; a Jira board view |
| Azure DevOps | Create issues with rich text and attachment carry-over; an Azure board view |
| ClickUp | Link existing tasks; a ClickUp board view |
| RabbitQA issues | An internal tracker for teams without an external one |
| TestRail | Push a run's results into a mapped TestRail project |
| CaseWriter | The shared test repository, and AI test case generation from an issue |
Permissions
TestPilot's own actions are gated on three groups of keys:
| Group | Covers |
|---|---|
testpilot:testset:* | Test plans and test runs |
testpilot:testresult:* | Test executions and their results |
testpilot:testcase:* | Test cases |
Issue actions use the cross-product integration:issue:* keys instead, because the same issue endpoints are shared with other modules.
Controls you lack the permission for are hidden or shown read-only. The backend re-checks every request.
Getting started
- Create a test plan for the release or sprint you are testing.
- Create a test run inside it and pick its test cases from the repository.
- Assign the executions across your team.
- Execute the tests and record results and evidence.
- Raise issues for failures.
- Generate a report when the run is done.
Next steps
- Quick Start - your first plan, run, and report
- Dashboard - monitor testing at a glance
- Best Practices - planning, execution, and reporting guidance
