AutoRunner Module
AutoRunner is RabbitQA's test automation orchestration module. It connects your automation sources, organizes scenarios into test plans, executes them, and reports the results back in one place.
How AutoRunner Is Organized
AutoRunner is workspace-first. Everything you see is scoped to the workspace selected in the RabbitQA shell.
| Level | What it is |
|---|---|
| Workspace | The owning scope. Test plans, run profiles, environments, and test data all belong to a workspace. |
| Source | An automation source inside the workspace: a connected repository, a Postman collection, or the workspace's AI source. |
| Scenario | One executable test. Scenarios live in a source and can be authored, imported, or AI-generated. |
| Test Plan | A workspace-owned selection of scenarios, which may come from more than one source. |
| Run | One execution of a test plan or of a single scenario, with steps, logs, artifacts, and results. |
Earlier releases called sources "projects" and test plans "test suites".
The API still uses the older projects and test-suites names in places, but the product surface is Sources and Test Plans.
Navigation
The AutoRunner sidebar contains the following entries.
| Sidebar item | Path | Documentation |
|---|---|---|
| Dashboard | /autorunner/dashboard | Dashboard |
| Scenario List | /autorunner/scenarios | Scenarios |
| Test Plans | /autorunner/plans | Test Plans |
| Test Runs | /autorunner/runs | Test Runs |
| Test Datas | /autorunner/test-datas | Test Datas |
| Issue Tracker | /autorunner/issues | Issue Tracker |
| Schedules | /autorunner/schedules | Schedules |
| Reports | /autorunner/analytics | Reports |
| Sources | /autorunner/sources | Sources |
| Mail Settings | /autorunner/mail-notification | Mail Settings |
| Settings | /autorunner/settings | Settings |
Scenario List, Test Plans, Test Runs, and Test Datas are workspace-level destinations and appear directly under Dashboard.
Some surfaces are opened from within these pages rather than from the sidebar:
- AI Studio — the authoring workspace for AI-generated scenarios, opened from a source.
- AI Editor — the code editor for repository-backed sources.
- Element Registry — the shared element and screen knowledge behind AI automation.
- Run Detail — opened from any run in Test Runs.
Framework Types
A source declares one framework type.
| Framework | Value |
|---|---|
| Gauge | GAUGE |
| Cucumber | CUCUMBER |
| Postman | POSTMAN |
| Robot Framework | ROBOT |
| AI Agent | AI_AGENT |
| SAP | SAP |
| Oracle | ORACLE |
| Logo Tiger | LOGO_TIGER |
| Record and Play | RECORD |
| JUnit | JUNIT |
| TestNG | TESTNG |
| xUnit | XUNIT |
Source Types
| Type | Value |
|---|---|
| Web | WEB |
| Desktop | DESKTOP |
| Mobile | MOBILE |
| Service | SERVICE |
| RoboClick | ROBOCLICK |
Key Capabilities
- Multi-source test plans — Select scenarios from several sources into one plan.
- AI scenario generation — Generate web and mobile automation with an AI agent, with human-in-the-loop questions, instructions, and pause/resume control.
- Element Registry — A shared catalog of screens and elements with locator versions, coverage, and a human-reviewed proposal queue.
- Self-healing review — Heal events raised during a run are proposed for review; you accept or reject each one.
- Run analysis — Steps, logs, network traces, screenshots, browser recordings, variables, and scenario definitions per run.
- Test data — Workspace environments, variables, and files, with masked secret values.
- Scheduling — Recurring runs for your test plans.
- API access — Start runs and read results from a pipeline through the AutoRunner API.
Where to Start
- Connect an automation source in Sources.
- Browse what the workspace already contains in Scenarios.
- Group scenarios into a plan in Test Plans.
- Run the plan and review the result in Test Runs and Run Detail.
The Quick Start walks through this end to end.
