Use this article to find the Evals that apply to a Release, run them, add more Evals to the Release, and understand why Batch Test is unavailable inside a Release.

To see which Evals apply to a Release, open the Release and click the Evals tab. The tab lists Evals in two groups:

Each Eval row shows its name, its run status, and a … menu. The run status can be Queued, Running (for example, 6/6 Running), or Not run. To hide or show a group, click its name. The Evals tab also shows a count of the Evals in each group.

To run an Eval inside a Release, click the run button on the Eval's row in the Evals tab. A run runs the Eval's Simulations (realistic test conversations) against your Release's changes instead of your live Fin Main setup. While an Eval runs, its row shows a stop button, which you can click to stop the run.

To add more Evals to the Release, click Add more Evals below the two groups.

To see all Evals while working inside a Release, select the Release in the switcher at the top left of the nav, then go to Test > Evals. The Evals page lists every Eval with its name, result, tags, last run date, and who last ran it. You can search Evals by name, add filters, and use the run or stop button next to an Eval name.

Batch Test is unavailable inside a Release because it is only available in Fin Main. When a Release is selected, hovering over Batch Test in the Test menu shows the message "Batch Test is only available in Fin Main." To use Batch Test, switch back to Fin Main using the switcher at the top left of the nav.