History & Attachments
Track execution history, review the change audit trail, and manage file attachments on test cases.
Execution History
The Execution Status tab on a test case detail view provides a comprehensive record of every time that test case has been executed across all test cycles. This gives you a longitudinal view of the test case's reliability and the feature it covers.
Reading the execution history table
Each row in the execution history table contains:
- Test Cycle — The title and ID of the cycle in which the test case was executed. Click the row to open that cycle's execute page for this test case.
- Status — The execution outcome:
Pass,Fail,Blocked, orNot Executed. - Version — The test case version that was executed. This column only appears when versioning is enabled for the project.
- Execution Date — The date and time of the execution, shown in your profile timezone.
- Executed By — The user who recorded the result, or Unassigned.
The actual result recorded for an execution is not shown in this table — open the cycle to read it.
Execution results are recorded in test cycles, not directly on the test case. The execution history tab aggregates results from all cycles for convenience. To run a test case, add it to a cycle and execute it there.
Change History
Every modification to a test case is recorded in its History tab, creating a complete audit trail. This is invaluable for understanding how a test case has evolved, who made changes, and when.
What changes are tracked
- Field updates — Any change to title, summary, priority, status, preconditions, labels, environment, automation ID, automated flag, or custom fields. The old value and new value are both recorded.
- Step changes — Adding, editing, deleting, or reordering test steps.
- Folder moves — Moving the test case from one folder to another.
- Attachment changes — Uploading or deleting attachments.
History entry format
Each history entry shows:
- Timestamp — When the change occurred.
- User — Who made the change (name and avatar).
- Change description — A human-readable summary of what changed. For field updates, this includes the old and new values (e.g., "Priority changed from Medium to High").
The change history is read-only and cannot be edited or deleted. It serves as a permanent audit record that supports compliance requirements and team accountability.
Attachments
Attach files to test cases to provide additional context — screenshots of expected UI states, test data files, design specifications, API response samples, log files, or any other supporting material.
Uploading attachments
- Open a test case and navigate to the Attachments tab.
- Drop files onto the dashed Drop file here or click to browse area, or click it to open your file picker. You can select several files at once.
- Each file is uploaded and appears in the attachment list. A toast reports how many succeeded and how many failed.
Allowed file types
Only the file types below can be attached. The list is an allowlist — anything not on it is rejected, whatever its extension.
| Category | Allowed |
|---|---|
| Images | .png, .jpg, .jpeg, .gif, .webp, .svg, .bmp, .tif / .tiff, .ico, .avif, .heic, .heif |
| Documents | .pdf, .doc, .docx, .xls, .xlsx, .csv, .txt, .md |
| Video | .mp4, .mov, .avi, .mkv, .webm |
Archives and data files are rejected. .zip, .rar, .7z, .tar, .gz, .json, .xml,
.ppt / .pptx and everything else not listed above are refused with Unsupported file type:
<type>. This trips people up when attaching an API response or a bundle of logs — zipping a
folder of screenshots does not get it past the check. Attach the files individually, or convert
the payload to .txt / .md / .csv.
The check runs on the file type your browser reports, not on the extension, and the file picker does not pre-filter — every file on your machine is selectable and only rejected after you choose it. A file whose type the browser cannot identify is refused as Unsupported file type: application/octet-stream.
Size and storage limits
| Limit | Value | What you see when you exceed it |
|---|---|---|
| File size | 50 MB per file | File exceeds 50MB limit — the file is refused and nothing is stored. |
| Attachments per test case | No limit | — |
| Organization storage | Your plan's storage allowance | Organization storage limit exceeded — the upload is blocked until you delete attachments or add storage. |
Storage is shared across the whole organization and counts every attachment in every project. See the pricing page for your plan's allowance.
Uploading several files at once is not all-or-nothing. Each file is checked and uploaded on its own, so a rejected file does not stop the rest — the toast tells you how many of the batch went through.
Managing attachments
Each attachment row shows the file name, size and the upload date. The uploader's name is not shown in this table — check the test case History tab to see who added a file. You can:
- View — Click the eye icon to open the file in a new browser tab.
- Download — Click the download icon to save the file locally. The file name itself is not a link.
- Delete — Click the delete icon () to permanently remove the attachment.
Deleting an attachment is permanent and cannot be undone. Make sure you have a local copy if you may need the file later.
See also
- Test Cases — Overview, creation, detail tabs, and field reference
- Test Steps — Define step-by-step execution procedures
- Folders & Organization — Organize test cases with folders, search, and filters
- Import & Export — CSV import and export
- Bulk Operations — Clone and bulk update test cases
- Versioning — Automatic version tracking and execution version recording
- Best Practices — Guidelines and FAQ