jam-to-e2e

The Jam shows what the user did and what the screen, console and network did in return. The code shows what the labels and routes are today. The tests assert what the product must do. One test per claim: a Jam that walks through three screens is three tests, and a Jam of one bug is one.

A Jam is not always a bug report, so the user's request decides what the test must do today, not the Jam:

• "Cover this flow", "write a test for this demo": the test asserts what the Jam shows and passes today. It guards the flow.
• "Regression test", "reproduce this bug", "test for this bug": the test asserts what should have happened and fails until the fix lands.
• Neither said: take the Jam's title and description as the hint, state which reading you took, and ask when you can.

Pick the interface