# Attach execution evidence to a TMS

Canonical: https://fairleadhq.com/docs/recorder/tms-evidence/

Updated: 2026-10-10
Publication state: published
Product version: Recorder source f6ed5b96

Agent summary: Use Test case to preserve an ID and result with the report, then attach reviewed evidence and enter the result in the TMS manually.

## Prerequisites

- Access to the relevant TMS case and run

## Inputs

- Reviewed files or approved accessible links

## Outputs

- Evidence mapped to the execution result

## Limitations

- Manual handoff only; no native TMS connector or automatic verdict synchronization

## Permissions

- Permission to update the case or run and share its evidence

## Privacy

- Review content and destination before sharing


Associate reviewed evidence with the correct case and run.

Select **Test case** and type the authoritative case ID before recording. Recorder stores that ID and offers Passed, Failed, or Blocked after Stop, but TMS lookup and delivery remain locked **Soon**. Attach evidence and enter the result through your TMS manually.

## Identify the execution

Open the correct case and run. Record the build, environment, browser, tester, execution time, and relevant test-data reference. Use the TMS's result fields for your assessment.

## Prepare the handoff

1. [Review the recording](https://fairleadhq.com/docs/recorder/review-redaction/) and download the files you need.
2. Map each folder or file to its case step or checkpoint.
3. Write expected and actual behavior, the outcome, and any skipped checks.
4. Attach the selected files using the TMS's attachment controls.

See [session and notes exports](https://fairleadhq.com/docs/recorder/bundle-contents/#session-summary-and-notes). Attach `session.md` and available `notes.md`, and enter the assessment in the TMS result fields.

## Example evidence set

For the [real sample](https://fairleadhq.com/docs/recorder/schema/#sample-reproduction-bundle), attach `session.md`, `notes.md`, `network.har`, and the relevant PNGs to your own case/run. Describe the failed expectation: leaving Blocked should clear the badge. Reference action 20 and HAR entries 4–5 for the last move, and explain that `003-area.png` has no lane heading. The supplied recording contains no TMS run reference; do not invent one or claim it was synchronized.

## Use links when appropriate

Use an approved stored-session link only if the intended reviewers can open it. Check project access and any extension or sign-in requirements. An extension-local viewer URL is not a shareable evidence link.

For files, confirm the TMS accepts the format and size. Open an attachment after uploading to ensure it is usable by the intended recipients.

## Explain multiple recordings

List checkpoint recordings in execution order. State where capture started and stopped, including gaps between segments. The [retained-timeline limit](https://fairleadhq.com/docs/recorder/developers/capture-support/#recording-retention) still applies; several files do not automatically prove continuous execution of the entire case.

## Record the result

Use [Record test outcomes](https://fairleadhq.com/docs/recorder/test-outcomes/) to distinguish passed, failed, blocked, and inconclusive. Link a defect if needed, but keep the execution result on the case/run. An attachment failure should be reported as a handoff problem, not silently treated as a complete evidence record.