An agent can give a different answer each time, take a different path to the same answer, and be right for the wrong reason. This site starts from one test with one expected result and climbs, one idea at a time, to rubrics, golden datasets, trace grading, judges, repeated trials and release gates. At each step it asks one question: what does this number let me claim?
A unit test runs once and gives the same result every time. An agent does not. The same input can give a different answer on the next run. Two runs can give the same answer, and only one of them checked the rules first. A team that tests an agent the way it tests other code gets a green result that says very little.
Task, case, trial, grader, rubric, score, threshold: each word gets one plain sentence and one small example before it is used. Then code, model and human graders, weighted scores, and the failures that no good prose may outweigh.
Output, trajectory and end state are three different things to grade. Traces and spans, a model as a judge and how to calibrate it, and five numbers that look alike and are not the same.
Repeated trials, at least one of k against all of k, intervals and sample size, a paired comparison with a baseline. Then the runner, the suites that may block a release, and evals on production traffic.
A synthetic underwriting agent with ten cases, followed on every page. A small Python eval harness that runs with no model, no network and no key. Eleven interactive labs, and seven eval tools read on their own documentation.