Skip to content
Honen Academy

Docs

Test an Agent with Evals

Evals runs an Agent against saved test cases. Each case contains input, optional files, scoring criteria, and a passing percentage. Use the results to compare changes to the Agent's instructions, resources, or model.

Prepare representative cases

First, configure and try the Agent in Console. Include ordinary tasks and cases where the Agent should report missing evidence. Use fictional or approved test data.

  1. Open Agents → Evals.
  2. Create a new eval.
  3. Select the Agent.
  4. Name the eval.
  5. Add a case.
  6. Enter its input values and files.
  7. Add criteria that describe observable results.
  8. Set each criterion's points.
  9. Set the case's passing percentage.
  10. Save the case.

An eval can contain up to 50 cases. For document tasks, include criteria for factual accuracy, required content, and usable output files. For example: “The feedback cites evidence from the supplied essay.” Avoid a criterion such as “The answer is good.”

Run and inspect the eval

  1. Select Preview for an initial test with read-only workspace access.
  2. Choose Save & run for a new or changed eval, or Run all for a saved eval.
  3. Keep the tab open while it starts the cases.
  4. Open a result to inspect its output and criterion scores.
  5. Use Activity to inspect the Agent's work.
  6. Open each generated document.
  7. Compare it with the supplied evidence.

Run all starts cases in sequence. A case already started continues on the server if you leave the page. Stop cancels the active case and prevents the page from starting more cases. Live runs can perform the actions allowed by the Agent. Review those permissions before you choose Live.

Compare results

Use the case's latest result and average to find recurring weaknesses. Open history to compare individual results and grouped runs. Use the Preview and Live filters to compare the same execution mode.

The summaries cover the most recent 300 case executions. The page indicates when older results exist. Failed, stopped, ungraded, and judge-error results are separate from numeric score averages. A judge error is not a zero score. Deleted cases remain in history but leave the current case summary.

Each run retains its scoring criteria. Review those criteria when comparing results from different dates. An automated score supports your review; inspect important answers and documents yourself.

Continue with Agent logs and analytics.