Skip to content
DOCS

Test Cases & Runs

AI generates a comprehensive test suite from your knowledge base. Review, run, edit, export, and analyze test cases — all from your project dashboard.

GUIDE

Working with test cases and runs

Section 1/ 06

Understanding test cases

Test cases are generated automatically from the knowledge base. Each test case describes a specific user scenario — like logging in, completing checkout, or searching for a product. Test cases include the steps to execute, expected outcomes, and the pages/flows they cover.

Test cases are organized by coverage area: happy paths, negative flows, edge cases, and visual regression checks. You can view all test cases from the project dashboard, filter by status (passing, failing, untested), and see which pages and flows each test case covers.

Section 2/ 06

Running tests and viewing results

Trigger a test run from the dashboard to execute all test cases against your application. Each run produces a detailed report showing which tests passed, failed, or encountered errors — with full screenshots, console logs, and timing data.

You can run tests manually on demand or configure GitHub webhook integration for automatic runs on every push. Test runs are executed in parallel for speed. Results stream in real-time — you can watch progress from the dashboard as each test case completes.

Section 3/ 06

Editing test cases

AI-generated test cases can be edited to better match your requirements. Modify steps, adjust expected outcomes, add assertions, or change the test name. Edits are preserved across re-exploration runs.

You can also disable individual test cases if they're not relevant, or mark them as expected failures. When the knowledge base is updated (via re-exploration or manual edits), new test cases may be generated while your custom edits remain intact.

Section 4/ 06

Deleting and managing test cases

Remove test cases that are irrelevant, duplicate, or no longer applicable. Deleted test cases can be regenerated later if the knowledge base still covers the associated flows.

Use bulk selection to delete or disable multiple test cases at once. You can also filter to find specific test cases by page, flow, or status before taking action.

Section 5/ 06

Exporting test cases and reports

Export your test suite as a structured report or integrate with external tools. Test cases can be exported in JSON or CSV format for use in other QA tools or for documentation.

Test run reports can be exported as PDF or shared via a unique link. Reports include pass/fail summaries, screenshots of failures, execution timings, and coverage metrics. Export to share with stakeholders or archive for compliance.

Section 6/ 06

Analyzing trends and coverage

The analytics dashboard shows pass/fail trends over time, flakiness detection, module-level coverage heatmaps, and regression frequency. Use these insights to focus on high-risk areas.

Flakiness detection flags tests that intermittently pass and fail — helping you identify unstable selectors or race conditions before they become a problem. Coverage heatmaps show which parts of your app are well-tested and which need more attention.

ACTIONS

What you can do with test cases and runs

Run tests

Execute all or selected test cases against your app

Re-run failed tests

Quickly retry only the tests that failed

Edit test steps

Modify AI-generated test case steps and assertions

Disable test cases

Temporarily skip irrelevant or expected-failure tests

Delete test cases

Remove unnecessary tests permanently

Export suite

Download test cases as JSON or CSV

Export run report

Share PDF reports with screenshots and metrics

View run history

Browse past test runs and compare results