Skip to content

Docs: add User Testing as promote-to-test-case surface #3776

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mintlify wants to merge 4 commits into
base: main
Choose a base branch
from
+4 −2
Open

Docs: add User Testing as promote-to-test-case surface #3776

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
e1765aa
Update docs/inspector/evals.mdx
mintlify[bot] Aug 7, 2026
5456b63
Merge branch 'main' into mintlify/docs-update-pr-3762-1786137034119
github-actions[bot] Aug 8, 2026
cc21a95
Merge branch 'main' into mintlify/docs-update-pr-3762-1786137034119
github-actions[bot] Aug 9, 2026
5a7c6ac
Merge branch 'main' into mintlify/docs-update-pr-3762-1786137034119
github-actions[bot] Aug 10, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions docs/inspector/evals.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -297,9 +297,11 @@ Any completed chat session can be turned into a test case without rewriting it f

**From the Playground** — Open the **Sessions** rail, hover a session, and click **Promote to test case**.

**From the Swarms tab** — Open a completed run, click a session row to select it, then click **Promote to test case** above the session viewer. The session must belong to a completed run attempt; sessions from in-progress runs show an error in the dialog instead of blocking at submit.
**From the Swarms tab** — Open a completed run, click a session row to select it, then click **Promote to test case** in the session detail pane. The session must belong to a completed run attempt; sessions from in-progress runs show an error in the dialog instead of blocking at submit.

In both cases the dialog shows the servers recorded for that session, lets you set a case title and suite name, and (when attachment pickers are enabled) lets you configure the server attachment and client host for the new suite.
**From User Testing** — Open a scenario's **Sessions** tab, select a session, and click **Promote to test case** in the session detail pane. Only project members can promote sessions; project guests can view sessions but the promote button is not shown to them.

In all cases the dialog shows the servers recorded for that session, lets you set a case title and suite name, and (when attachment pickers are enabled) lets you configure the server attachment and client host for the new suite.

## Generating cases from your tools

Expand Down
Loading