← Blog
Chatbots & Assistants

What Is Prompt Regression Testing? (2026): Did the Last Good Answer Still Pass?

By Andrew · October 24, 2026

Prompt regression testing is a re-run of a frozen set of prompts, scored the same way as last time, so you can see which answers got worse after a prompt edit, a model swap, or a retrieval change. A new demo can look better and still break the refund case you already accepted. The regression is the comparison to that accepted run. If you have no saved baseline, you have a fresh test, and a fresh test cannot tell you what you lost.

The habit of choosing the tasks is what AI eval testing is. The files and the runner are what an AI eval harness is. The wording you are allowed to change is what prompt versioning is. A wrong sentence that was not in the source is what an AI hallucination is.

Prices are US list prices excluding tax from directory pages checked October 16, 2026. Published October 24, 2026. The directory does not list a prompt-regression product fee, so this page does not invent one. We did not score any model.

What you keep from the last good run

You saveWhy the next run needs itLeave it out when
The exact prompt text, with a version idA paraphrase is a different testYou are still brainstorming wording in a doc
The inputs: the ticket, the schema, the chunkThe answer depends on what the model sawThe input is a secret you are not allowed to store
The score rule, in one sentence“Looks fine” cannot fail a buildYou have not agreed what “wrong” means
The last passing result, or the last scoreRegression is a diffThis is the first time you have run the case
Who may accept a dropA quieter failure still ships if nobody owns the exceptionThe change is a local experiment that will not merge
flowchart TD
  change["A prompt, a model, or the retrieved pages change"] --> run["Re-run the frozen set"]
  run --> diff{"Does a case that passed last time still pass?"}
  diff -->|Yes| ship["You may widen the change"]
  diff -->|No| stop["Keep the last version until a person accepts the drop"]
  stop --> note["Write which case failed and why you allowed it"]

A green average can hide one broken case. Report the cases that flipped, not only the mean. The person who may accept a drop is what human-in-the-loop AI is.

Where the baseline is written

The long case file. Claude Pro is $20 a month, or $17 billed annually ($200 up front). Put the frozen prompts and the score rule in a Project so a later edit cannot quietly rewrite the test. The review is Claude review.

The team’s default chat. ChatGPT Plus is $20 a month. Business is $20 a user a month billed annually for two or more users, or $25 billed monthly, when the cases include customer text. The ladder is ChatGPT Go vs Plus vs Pro.

The change, if it lives in the repo. Cursor Plus for new customers is $8 a month, or $80 a year. Premium is $30 a month. The regression still needs a command you can run again. The editor is not the harness. The invoice is Cursor pricing explained.

A table of pass and fail the team can reopen. Hex Professional is $36 an editor a month when the scores should be a notebook, not a chat scroll. Community is free, with a Hex agent trial and small compute. The invoice is Hex pricing explained.

A prompt that holds the line, for drafting the score rule only:

“Here are ten cases and the last accepted answer for each. Write a pass rule a person can apply without taste. If a case has no accepted answer, write Missing. Do not invent a score.”

What a regression is allowed to block

Block a ship when a named case flips from pass to fail and nobody has accepted that flip in writing. A model upgrade is a change. A temperature tweak is a change. A new help article in the retrieval set is a change. Each one gets the same re-run.

Do not block a ship because a case looks different and the score rule never said that difference was a failure. Style drift without a rule is a note, not a red build. The switch that can keep the new prompt off production while you argue is what AI feature flags are. The live slice, once you do expose it, is what AI canary releases are.

FAQ

Is a regression the same as an eval?

An eval is the set and the score. A regression is the next run compared with a run you already accepted. You can have an eval on day one. You can have a regression only after you have a baseline.

How many cases do I need?

Enough that a failure you would be ashamed to ship is in the set. Ten honest cases beat two hundred copied from a public benchmark you do not serve. Add a case when production breaks in a way the set missed.

Can the model grade its own regression?

It can propose a score. A person, or a check that does not depend on the same prompt you just changed, confirms the flip. A model grading a change to itself is a review with a conflict.

What if the new model is better on average and worse on one case?

Say both. The average is not permission to drop the case. Either accept the drop, with a name and a date, or keep the last prompt for that path.

Last verified

October 16, 2026 for Claude, ChatGPT, Cursor, and Hex prices named above. No prompt-regression vendor fee is recorded in the directory. Published October 24, 2026.

Sources: Claude pricing, ChatGPT pricing, Cursor pricing.

Published by Andrew for AI Tools Optimizer.

Claude is in the chatbots and assistants directory. Directory pages may use affiliate links. A purchase through them may earn us a commission at no extra cost to you.

Disclosure: this post may contain affiliate links. If you buy through them we may earn a commission at no extra cost to you.

Tools mentioned in this post