Recording Results
Recording a result is the core action of test execution — set the overall status, mark individual steps, add comments and attachments, log elapsed time, and link defects. Every result is timestamped, attributed to the tester, and preserved in a permanent history.
Think of it as filing an inspection report
Each test case is an inspection item. You check off each step (pass, fail, block, or skip), note any issues you find, attach evidence (screenshots, logs), record how long it took, and file defect tickets for anything that needs fixing. The report is stamped with your name and the time, and it goes into a permanent file that anyone can review later.
Opening the Add Result modal
- Open a run from the TEST RUNS tab.
- On the Results tab, click a test case in the results table to open the case details panel.
- Click the Add Result button at the top of the panel.
Result fields
| Field | Required | Description |
|---|---|---|
| Status | Yes | The overall outcome of the test execution. Choose from statuses that have the Available for Run Results scope enabled. See Scope Availability. |
| Step Results | No | Per-step outcomes. Only available when the test case includes a STEPS field. See Step-by-step results below. |
| Comment | No | A rich-text note with formatting, inline images, and attachments. Use it to describe what happened, capture observations, or explain the outcome. |
| Elapsed Time | No | How long the execution took, in seconds. Useful for tracking performance trends across runs. |
| Assigned To | No | The user responsible for this case in the run. Selecting a user here updates the Assigned To column in the results table. |
| Custom Fields | No | Template-defined fields attached to the test case. Values entered here are stored with the result. |
| Attachments | No | Files uploaded as evidence — screenshots, logs, recordings. Drag and drop or click to browse. |
| External Issues | No | Links to issues in external trackers (Jira, GitHub, Azure DevOps, etc.). See Linking external issues below. |
Step-by-step results
When the test case includes a STEPS field, each step is displayed in the Add Result modal with its instruction and expected result. For each step you can set:
| Step status | Meaning |
|---|---|
| Passed | The step produced the expected result. |
| Failed | The step did not produce the expected result. |
| Blocked | The step could not be executed due to a dependency or environment issue. |
| Untested | The step was not executed (default). |
Each step also has an optional note field for recording observations specific to that step.
Step results are independent of the overall status. Setting every step to Passed does not automatically set the overall status. The overall status is what counts for progress tracking, completion rates, and the status grid. Set it explicitly.
Attaching files
Drag files into the attachments area or click to open a file browser. Files are uploaded securely via presigned URLs. Attached files appear in the result history with download links. You can also paste or drag images directly into the comment editor for inline display.
Linking external issues
- Click Add Issue in the External Issues section of the modal.
- Select the Source — the integration (e.g. Jira, GitHub) configured in Integration Sources.
- Choose a Relation type — e.g. “Defect”, “Related”, “Blocks”.
- Enter the External Key or URL of the issue.
- The issue title and status are fetched automatically when available.
Linked issues appear on the case’s Issues sub-tab and the run’s Issues tab, providing end-to-end traceability from test result to defect.
Saving a result
Click Save to record the result. The results table updates immediately — the case row shows the new status, and the progress bar recalculates. Multiple results can be recorded for the same case; the most recent result determines the current status shown in the table.
Quick status change vs full result
| Approach | What it records | When to use |
|---|---|---|
| Quick status change | Status only — no steps, comments, attachments, or issues. | Rapid triage or bulk marking (e.g. marking untested cases as Blocked). |
| Full Add Result modal | Status, step results, comment, elapsed time, custom fields, attachments, and issue links. | Auditable test execution with full evidence trail. |
Quick status changes record no evidence. They do not capture step results, comments, or attachments. For traceable, auditable test execution, use the full Add Result modal.
Result history
Every result recorded for a case is preserved permanently in a chronological timeline, visible in the case details panel’s Results sub-tab. The most recent result determines the case’s current status. Previous results are never overwritten or deleted — they provide a complete audit trail of every execution attempt.