Test spec
A test spec is a named collection of test cases within a project.
Test case structure
| Field | Required | Description |
|---|---|---|
| Domain | ✓ | Test domain (e.g. Authentication, Payment) |
| Layer | ✓ | Test layer (e.g. UI, API, Unit) |
| Quality dimension | ✓ | Test perspective (e.g. Functionality, Performance, Security) |
| Risk | ✓ | Risk level associated with the test target |
| Priority | ✓ | Execution priority |
| Test subject | ✓ | What is being tested |
| Preconditions | — | Required setup before execution |
| Steps | ✓ | Step-by-step actions (up to 100 steps per case) |
| Expected result | ✓ | Expected outcome of the test |
| Notes | — | Additional remarks |
Images (jpg / png, up to 5 MB each) can be attached to any test case and are displayed as thumbnails in the case list and report views.
Change history
Every create, update, or delete operation on a test case is recorded as an immutable event. You can:
- Restore to a point in time — roll back all test cases in the spec to their state at any past timestamp
- Restore a single case — restore one case from a specific past event, without affecting the rest of the spec
Dictionary
A project-level dictionary stores reusable test data (URLs, credentials, form inputs, etc.). Reference dictionary entries inside any test case field using {{key}} notation. When a test case is saved, undefined key references are detected and flagged with a non-blocking warning.
Dictionary values are resolved and highlighted when viewing the test case table and report detail pages. Hovering over a resolved value shows the original {{key}} notation.
Export
Test specs can be exported to CSV (UTF-8 with BOM, gzip-compressed). The export includes test subject, preconditions, steps, expected result, and notes for each test case.