Projects
Create, organize, and monitor automation projects across multiple frameworks and project types.
What are AutoRunner Projects?
An AutoRunner project is the top-level container for your test automation effort. Each project is configured with a specific test framework and project type, and contains one or more test suites. Projects track health metrics and provide team access controls.
Creating a Project
- Navigate to AutoRunner > Projects.
- Click the Create Project button.
- Fill in the required fields:
| Field | Required | Description |
|---|---|---|
| Project Name | Yes | Unique, descriptive name for the project |
| Framework | Yes | Test framework (Gauge, Cucumber, Postman, Robot, AI Agent, SAP, Oracle, Logo Tiger) |
| Project Type | Yes | Application type: Web, Desktop, Mobile, or Service |
| Description | No | Brief description of the project scope |
| Repository URL | No | Git repository URL for source-controlled tests |
| Team Members | No | Assign team members with access to the project |
- Click Create to save.
- Web — Browser-based applications tested with Gauge, Cucumber, or Robot
- Desktop — Desktop applications tested with SAP, Oracle, or Logo Tiger
- Mobile — Mobile apps tested via Appium-compatible frameworks
- Service — APIs and microservices tested with Postman or Robot
View Modes
AutoRunner offers two ways to browse your projects:
Card Grid View
Displays projects as cards with key metrics visible at a glance:
- Project name and framework icon
- Pass rate percentage with color indicator
- Last run date and status
- Suite count
Table View
A data-dense table layout ideal for managing large numbers of projects. Columns include project name, framework, type, pass rate, total runs, last run date, and status.
Toggle between views using the Grid/Table buttons in the toolbar.
Project Health KPIs
Each project is assigned a health status based on recent test results:
| Health Status | Criteria | Color |
|---|---|---|
| Healthy | Pass rate ≥ 90% with recent activity | Green |
| At Risk | Pass rate between 70–89% | Yellow |
| Critical | Pass rate below 70% or consecutive failures | Red |
| Inactive | No test runs in the last 30 days | Gray |
The KPI row at the top of the Projects page aggregates these statuses:
- Total number of Healthy, At Risk, Critical, and Inactive projects
- Overall pass rate across all projects
- Total run count for the selected time period
Project Detail Page
Click a project card to open the detail page with:
- Suites — List of test suites within the project
- Runs — Run history with status, duration, and pass rate
- Schedules — Scheduled runs configured for the project
- Settings — Project configuration and team access
- Metrics — Health metrics and trend charts
Project Settings
Access project settings from the detail page toolbar:
| Setting | Description |
|---|---|
| General | Edit project name, description, and type |
| Framework | View or change the test framework configuration |
| Repository | Configure SCM integration (Git URL, branch, credentials) |
| Drivers | Select and configure browser or device drivers |
| Environment | Define environment variables and target URLs |
| Notifications | Configure email and webhook notifications |
| Team Access | Manage team member roles and permissions |
Team Access
Control who can view, edit, and execute tests within a project:
- Owner — Full control including deletion
- Editor — Create, edit, and run suites and scenarios
- Viewer — Read-only access to runs and reports
Assign team members during project creation or from the Settings > Team Access tab.
Next Steps
- BDD Scenarios — Write test scenarios for your project
- Test Runner — Execute tests and monitor results
- Scheduling — Set up recurring runs for your project
