ENES

AI evals

Tests you write for your own AI app to check it does its job, before and after changes.

A list of test inputs goes through an AI app; each output is graded by code, by another model acting as judge, or by a person, and the results add up to a score

Evals (short for evaluations) are the tests of an AI product. You collect a set of realistic inputs, run your system on them and score the outputs automatically. Unlike a public AI benchmark, which compares models on general skills, your evals measure the thing you care about: does the support bot answer refund questions correctly, does the summarizer keep the clause that matters.

Scoring comes in three flavors. Some checks are plain code: is the output valid JSON, does it mention the right order number, does the generated code pass its tests. Some use a second model as the grader, known as LLM-as-a-judge, with a clear rubric like "does the answer cite the policy and stay polite?". And some need people, who also make sure the automatic graders agree with human judgment.

Evals matter because an LLM's behavior is hard to predict, and a small change can break things far away. A new prompt that fixes one case may quietly ruin ten others; a new model version may be smarter overall but worse at your format. With a good eval set you can change the prompt, the model or the retrieval and know within minutes whether things got better or worse, instead of finding out from users. A useful set can start small, with a few dozen real examples, and grow every time something fails in production.

Keep in mind

Go deeper

Related terms

More in AI