History & Attachments

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 name of the cycle in which the test case was executed. Click to navigate to the cycle.
• Result — The execution outcome: Passed, Failed, Blocked, Skipped, or Not Run.
• Executed By — The team member who performed or recorded the execution.
• Executed At — The date and time of the execution.
• Comment — Any notes the executor added during execution (e.g., failure details, environment info).

Execution history is sorted newest first by default. If a test case has been executed many times, you can quickly see whether recent runs are passing or if there is a regression pattern.

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, description, priority, status, type, preconditions, labels, environment, automation ID, automation status, 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").

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

1. Open a test case and navigate to the Attachments tab.
2. Click Upload or drag and drop files into the upload area.
3. The file is uploaded and appears in the attachment list immediately.

Supported file types and limits

Maximum file size: 10 MB per file. There is no limit on the number of attachments per test case, but the total storage across the project is subject to your plan limits.

Managing attachments

Each attachment in the list shows the file name, size, upload date, and the user who uploaded it. You can:

• Download — Click the file name or the download icon to save the file locally.
• Delete — Click the delete icon () to permanently remove the attachment.

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
• Best Practices — Guidelines and FAQ