Commit-Based Testing
Commit suites automatically select and run the tests most relevant to a specific git commit. Use them for pre-merge verification and post-deploy checks.
How It Works
When you create a commit suite, DebuggAI:
- Receives the commit hash and your changes info (diff or JSON)
- Analyzes what changed in the repository
- Automatically selects the E2E tests that cover those changes
- Groups them into a suite tied to that commit
No manual test selection needed — the AI picks the relevant tests based on what changed.
Creating a Commit Suite
From the Suites page, open the Create Commit Suite dialog:
| Field | Required | Description |
|---|---|---|
| Repository Name | Yes | e.g., my-app |
| Repository Path | Yes | e.g., /path/to/repo |
| Commit Hash | Yes | Full or short hash |
| Title | No | Human-readable label |
| Description | No | Context about the commit |
| Changes Info | No | Upload a JSON/diff file or paste changes manually |
Providing detailed changes info improves test selection accuracy.
Running a Commit Suite
Once created, open the suite and click Run. All selected tests execute as a group.
Track progress in the Run History tab — status moves from Pending to Running to Completed or Error. Each run shows duration, who started it, step count, and a link to the full run output.
Commit Suite vs Regular Suite
| Regular | Commit | |
|---|---|---|
| Test selection | Manual | Automatic (AI) |
| Tied to | Project | Commit hash |
| Use case | Organizing tests by feature | CI/CD, pre-merge verification |
| Creation | Manual | Via dialog with commit info |
Viewing Commit Info
On the suite detail page, commit suites show a Commit info card in the left panel with the full commit hash and a summary of the changes used to select tests.
Workflow: Pre-Merge Verification
- Push your branch
- Create a commit suite with the branch's HEAD commit hash
- Paste or upload the diff from your PR
- Run the suite
- Review results before merging