Test Suites
A suite is a collection of E2E tests that run together. DebuggAI has two types: Regular and Commit.
Suite Types
| Regular | Commit | |
|---|---|---|
| Test selection | Manual | Automatic (AI) |
| Tied to | Project | Git commit hash |
| Use case | Organizing tests by feature | CI/CD, pre-merge verification |
Regular suites are collections you assemble manually — e.g., all authentication tests, all checkout tests.
Commit suites are auto-generated for a specific commit. DebuggAI analyzes what changed and selects the relevant tests automatically.
Viewing Suites
Navigate to a project and open Functional Tests from the sidebar. Suites appear in the left panel. A global suites list is also accessible at /suites (direct URL). It shows:
- Stats: Total suites (with regular/commit breakdown), Running, Completed, Failed
- Table columns: Type, Name, Description, Project, Test count, Status, Commit hash (commit suites only), Created by, Date
Status Reference
| Status | Meaning |
|---|---|
| Never Run | Not yet executed |
| Pending | Queued for execution |
| Running | Currently executing |
| Completed | Finished execution |
| Failed | One or more tests failed |
Filter by suite type (All / Regular / Commit), status, or commit hash. Use the search bar to find by name or description.
Suite Detail Page
The detail page has two panels:
Left panel
- Status card
- Commit info card (commit suites only — full hash and changes summary)
- Tests tab: All tests in the suite with name, description, and link to view each test
- Run History tab: Past runs with status, duration, started by, step count, and link to the full run
Right panel
- Suite info: project, test count, UUID
- Timeline: created and modified dates
- Quick actions
Running a Suite
Open the suite and click Run. All tests execute as a group. Track progress in the Run History tab — status moves from Pending to Running to Completed or Failed.
Creating a Regular Suite
Open a project, go to Functional Tests, and click the + button in the test suites sidebar. Fill in:
- Name (required)
- Description (optional)
Creating a Commit Suite
Use the Create Commit Suite dialog and provide:
- Repository Name — e.g.,
my-app - Repository Path — e.g.,
/path/to/repo - Commit Hash — full or short hash
- Title — optional
- Description — optional
- Changes Info — upload a JSON or diff file, or paste changes manually
DebuggAI uses the commit information to automatically select and associate the relevant E2E tests.
For commit-based testing details, see Commit Testing.