liveBook · Manning

Evaluation suite

As explained in Introduction to Generative AI, Second Edition

An evaluation suite is a coordinated collection of tests and criteria for assessing model responses on a task.

An evaluation suite is a set of assessments used to compare model responses against criteria across representative task contexts. Running the assessments after prompt or model changes can reveal regressions before they reach a product. section 7.10 section 7.12

Testing listing descriptions

A listing generator’s prompt is revised to improve accuracy and instruction-following. Running all the evaluations after each change helps catch improvements in one measure that come at the expense of another. section 7.10

Table 7.6 Methods of generative AI evaluations

Type of evaluation

When to use

Advantages

Disadvantages

Human preference or judgment

Before an LLM judge is validated, or to confirm hypotheses about human preferences

  • Typically close to ground truth for preferences and judgment (if raters are trained in the task)
  • Expensive
  • Not scalable

Heuristic evaluation or verifier

When “checking” the response or computing a metric can be done deterministically (such as with multiple-choice questions or measures like response length)

  • Cheapest
  • Easiest to scale
  • Always accurate, since metric is objective
  • Only applicable to a narrow subset of evaluations

LLM as judge

When the judgment of the response is for any nonverifiable or subjective quality

  • More expensive than heuristics due to inference costs, but cheaper than humans
  • Scalable
  • Annotators may have biases or be fooled by reward hacking

A/B test

When interested in user preferences and behavior in a live production setting

  • Number of data points is orders of magnitude higher
  • Ground truth for product impact
  • Requires users and a production environment
  • It can be difficult to attribute changes due to other factors in usage, like seasonality

Compare human judgment, deterministic checks, and LLM judges by their use cases and tradeoffs when choosing evaluation methods. section 7.10

Evaluation scores do not necessarily show what users prefer; that is better measured through production A/B testing. LLM judges can also show biases or reward outputs that score well without meeting the intended goal, so their performance needs regular checking. section 7.10

How Introduction to Generative AI, Second Edition covers it

How deep it goes
Describes repeated comparisons and the need to run valued evaluations, but gives no procedure for building a suite.
Examples
Uses a real-estate listing generator and prompt revisions to illustrate checking response quality across evaluations.
What you can do after
Evaluate prompt or model changes against sample task contexts and detect regressions before they reach a product.
How it connects
Links prompt engineering and regression testing with LLM judges and production A/B testing.

Also explained in

Compare how 11 books explain evaluation suite →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Introduction to Generative AI, Second Edition. The section links point to the parts of the book it draws on.