LLM Evaluation Glossary: Prompt Testing Terms, Defined

On this page

This glossary defines the terms people use when they test prompts and evaluate LLM outputs. Each entry starts with a one-sentence definition you can quote, then explains why the term matters in practice and links to the guide that covers it in depth. The definitions are tool-neutral; where Litmiq behaves in a specific way, the entry says so.

The short answer

Prompt testing means running a prompt on a fixed set of test cases and checking the outputs against expected behavior. The key ideas are the test case, the expected behavior, the baseline you compare against, and the judge or deterministic check that scores each output. Most mistakes come from vague expected behavior, too few cases, or trusting judge scores without reading the outputs.

Key numbers

  • Re-running the 11 security cases gave the same pass/fail on 130 of 132 model–case pairs at temperature 0; 2 flipped. Run important cases more than once. (Litmiq LLM Reliability Benchmark, 12 Nov 2026)
  • The LLM judge (gpt-oss-120b, same prompt as the app) scored that fenced JSON 2/10 for accuracy but 9/10 for helpfulness: read per-metric scores, not only the average. (Litmiq recorded demo run, 13 Nov 2026)

Core concepts

LLM evaluation (eval)

An LLM evaluation, or eval, is a repeatable test that measures how well a model or LLM application performs on a defined set of inputs. An eval has three parts: the inputs, a way to produce outputs (a prompt and a model), and a way to score them. "Eval" can mean a single test suite or the whole practice of measuring quality, including monitoring production traffic.

Prompt evaluation

Prompt evaluation is measuring how well a specific prompt makes a model behave on representative inputs. It holds the application around the prompt fixed and asks one question: is this prompt (and model) good enough for these cases? It is narrower and faster than evaluating a whole application with retrieval and tools.

Prompt testing

Prompt testing is running a prompt on a fixed set of test cases and checking each output against what it should do. It borrows the idea of unit tests from software: the same cases, run again after every change, tell you what broke. See prompt regression testing.

System prompt

A system prompt is the instruction text that sets a model's role, rules and output format before any user message. Most prompt tests hold the system prompt under test and vary the user message. In Litmiq, every test case runs against the one system prompt in the setup.

Test case

A test case is one input you send to the prompt, usually paired with a description of what a good answer must do. Good test cases come from real requests, known edge cases and past failures. In a single-turn test, a case is one user message.

Test suite

A test suite is the set of test cases you run together to judge a prompt. Five to twenty cases is a useful start; grow it by adding a case every time a real failure appears. Ready-made illustrative suites are on the templates page.

Expected behavior

Expected behavior is a short, checkable description of what the answer to a test case must do and must not do, rather than its exact wording. "Must say the 30-day window has passed; must not promise a refund" can be checked by a person or a judge; "a good answer" cannot. See how to write expected behavior.

Reference answer (golden answer)

A reference answer is a known-good output stored with a test case so new outputs can be compared to it. References suit tasks with one right answer, such as extraction or classification. For open-ended replies, expected behavior is usually more useful than a fixed reference text.

Baseline

A baseline is a saved run of your test suite on the current prompt and model, used as the point of comparison for the next change. Without a baseline, you can't say whether a score went down. In Litmiq, the JSON export of a run serves as a baseline.

Prompt regression

A prompt regression is a change to a prompt or model that makes some outputs worse than before. Typical causes are an added instruction that interferes with an old one, a model swap, or an edge case nobody re-checked.

Regression testing

Regression testing is re-running the same test suite after every change and comparing the results with the baseline to catch anything that got worse. For prompts, read every case whose score dropped; scores show where to look, not what happened.

Single-turn test

A single-turn test checks one reply to one user message, with no earlier conversation. Single-turn tests are fast and easy to read, but they can't catch problems that appear only later in a conversation. Litmiq runs single-turn tests.

Scoring and judges

LLM-as-a-judge

LLM-as-a-judge is using one language model to score or compare another model's outputs against criteria you write. It scales judgment calls such as tone and helpfulness that code can't check, but it inherits model biases, so its scores are estimates. See the LLM-as-a-judge guide.

Scoring criteria (rubric)

Scoring criteria, or a rubric, are the written rules a judge or reviewer uses to decide how good an output is. Specific, anchored criteria ("10 = states the policy and offers a next step; 3 = invents a policy") give more consistent scores than general ones ("be helpful"). In Litmiq, your criteria guide the judge while it reports four fixed scores.

Per-metric score

A per-metric score rates one quality of an output, such as accuracy or tone, separately from the others. Separate scores show what changed: a prompt edit might raise conciseness and lower accuracy. Litmiq's judge scores accuracy, tone, helpfulness and conciseness from 0 to 10, each with a reason.

Pairwise comparison

Pairwise comparison asks a judge or person which of two outputs for the same input is better, instead of scoring each alone. It is often more consistent than absolute scores, but it only tells you which is better, not whether either is good enough.

Deterministic check (assertion)

A deterministic check is a rule code can verify the same way every time, such as "the output parses as JSON" or "the reply is under 80 words". Use code checks for anything exact, and judges only for judgment calls. The JSON extraction guide includes an offline checker script.

Unscored result

An unscored result is an output the judge failed to score, for example because its reply could not be parsed. Marking it unscored, instead of filling in a default number, keeps averages honest. Litmiq marks these results unscored.

Judge calibration

Judge calibration is checking a judge's scores against your own labels on a sample of outputs, then adjusting the criteria until they agree. An uncalibrated judge can be confidently wrong in the same direction every time.

Failure modes and biases

Leniency bias

Leniency bias is a judge's tendency to give high scores to outputs that are merely acceptable. It compresses scores toward the top of the scale, so real drops look small. Anchoring each score level in the criteria reduces it.

Length (verbosity) bias

Length bias is a judge's tendency to prefer longer answers regardless of whether the extra words help. Counter it with a conciseness criterion or a deterministic length check.

Self-preference bias

Self-preference bias is a judge model's tendency to rate outputs from its own model family more favorably. It matters most when you compare models; read the outputs yourself before choosing one.

Non-determinism (run-to-run variance)

Non-determinism means the same prompt and input can produce different outputs, and different scores, on different runs. One good sample proves little; treat small score changes as noise and re-run before drawing conclusions.

Hallucination

A hallucination is an output that states something false or unsupported as if it were true, such as an invented policy or number. Test for it with cases where the right answer is "I don't have that information," and say so in the expected behavior.

Over-refusal

Over-refusal is when a prompt makes the model decline legitimate requests because its rules are too broad. Include benign cases that sit close to your restricted topics so you notice when a safety instruction overreaches.

Prompt injection

Prompt injection is user input written to override the system prompt's instructions, such as "ignore previous instructions". Single-turn injection cases with benign controls are in the prompt injection playbook.

System prompt leak

A system prompt leak is an output that reveals the hidden system prompt, in whole or in part. It is a common goal of injection attempts and is easy to test with a canary string.

Canary string

A canary string is a unique, meaningless token placed in a system prompt so that any output containing it proves the prompt leaked. Checking for an exact string is deterministic, so it doesn't depend on a judge.

Workflow and tooling

Offline evaluation

Offline evaluation runs a prompt or application on a prepared test set before release, without real users. Prompt testing in a browser or a CI job is offline evaluation.

Online evaluation

Online evaluation scores real production traffic as it happens, usually on a sample of requests. It catches problems your test set didn't anticipate and needs a tracing or observability platform. Litmiq doesn't do online evaluation.

Side-by-side comparison

A side-by-side comparison shows outputs from different models or prompt versions for the same input next to each other. It makes differences in tone, length and correctness easy to see. In Litmiq, every case runs on every selected OpenAI model and the outputs line up per case.

CI eval gate

A CI eval gate is an automated test run in continuous integration that blocks a change from merging when eval results fall below a threshold. Code-first tools such as Promptfoo and DeepEval are built for this; see prompt testing tools compared.

Red teaming

Red teaming is deliberately attacking an LLM application with adversarial inputs to find security and safety failures before others do. Dedicated red-team tools generate many attacks; a small hand-written injection suite is a useful first step.

Bring your own key (BYOK)

Bring your own key means a tool uses your own model-provider API key, so the provider bills you directly for usage. In Litmiq, your OpenAI key stays in your browser's localStorage and is sent only to OpenAI.

Eval cost

Eval cost is what a test run spends on model calls: generating every output plus any judge calls to score them. Count calls before you run: in Litmiq, cases × selected models gives the model calls, plus up to the same number of judge calls. Ten cases on two models is 20 model calls plus up to 20 judge calls.

Limits of this glossary

Get model deprecation alerts

We email you when OpenAI, Anthropic or Google publish a new shutdown date for a model on our tracker. Sent by hand from hello@litmiq.com, a few times a month at most. Unsubscribe by replying.

We store only your email, through our form provider. See the privacy policy.

Try it in Litmiq

Paste your system prompt, add a few test cases and compare OpenAI models side by side. Runs in your browser with your own OpenAI key.

  • Free, no signup
  • Runs in your browser
  • Your OpenAI key, sent only to OpenAI

Follow Litmiq on LinkedIn

Litmiq Pro

Saved suites, CI on a schedule and regression alerts for $19/month. The app stays free.

See pricing →

Related guides

Compare & reference

Share this guide