Test Still Expects The Old Value

What goes wrong

Behaviour, a version string, or UI text is changed on purpose, but a test that directly depends on it still expects the old literal. Usually the suite goes red at once; if that test only runs when an optional environment (real database, browser) is available, it is skipped elsewhere and the stale expectation quietly lives on.

Example

The button text changes from 'Submit' to 'Send', and the test still asserts that 'Submit' is on screen.

Not to be confused with

Not a test correctly catching an unintended regression, not a stale pointer to evidence in docs (Drifting Evidence Pointer), and not an expected value that follows the code and stays green (Self Derived Expected Value).

Discovered by

@sks24git GitHub

Field notes · 4

@sks24git2026-11-03beat 3 review rounds

A term moved from code into a data file, but an old test still checks the old date by hand. The first time someone extends the term in the file, the build breaks for every change.

a search tool tests for a literal when you move it. Copies in tests outlive the source.
Read the value in the test, do not retype it. A typed copy goes stale.

@sks24git2026-11-03

A CI change cuts one test pool and grows another, but a sibling test still counts the old pools by hand. A gate also waits for a job that branches made before the change will never run.

Read counts from the config, not from the test. A copied number goes stale on the next change.
Judge a run by the jobs it ran. Old branches still run their old config.

@sks24git2026-10-30beat 1 review round

A run snapshot gained a new field, but a database test still compared its keys to a fixed set. The pull request checks skipped that test, so the main branch would turn red after merge.

a search tool for exact-set checks when you add a field. Key equality breaks far from the change.
Run the slow tests your change can reach. Fast checks skip them.

@sks24git2026-08-13

A file staged by directory instead of by name carried a sibling change's work-in-progress into a branch without the test that pinned it. Every full-checkout test run stayed green, because the disk held both halves — so the branch's own HEAD was red in the one state nobody runs.

Stage by name, never by directory. A shared checkout puts other people's unfinished work one glob away from your commit.
Test what the branch contains, not what your disk holds. Stash the files that are not yours and run again — that is the state CI will see.
A number meaning another module's window must be imported from it. Retyped, it silently stops honouring the knob an operator turns.