This is the payoff of everything so far. A UI test usually cares about one

behavior — does this article render? — but reaching that state through the UI means

logging in, opening the editor, filling four fields, and publishing, every single

time. That's slow and, worse, it makes the test fail for reasons unrelated to what

it's checking.