OAuth tests often fail in a deceptively reassuring way: the provider returns a valid authorization code, the callback succeeds, and the test reports a green login. But which browser started that flow? Which test identity was attached to it? Was the code fresh, or did a retry consume an older response?
The answer should not depend on a shared inbox, a lucky timing window, or a test runner guessing which message is newest. OAuth test data needs the same boundaries as production data. A temporary mailbox can make setup convenient, but it does not prove that a callback belongs to the browser session that requested it.
Why a valid code is not enough
An authorization code proves that an identity provider issued something for an authorization request. It does not, by itself, prove that the current browser initiated that request.…