OAuth tests can pass while proving the wrong thing. A browser starts a login, an identity provider redirects back, and a test sees a successful session. But if two workers share a browser context, or an old callback is accepted, the green result may belong to another flow.
The security question is not only “did authentication complete?” It is “did this browser, this authorization request, and this account complete the same flow?” I treat that as a browser-binding check. It is a small addition to a test fixture, but it makes session mix-ups and replay-like bugs much easier to see.
The browser-binding problem
An OAuth browser test usually has at least four identities:
the test worker and its run ID
the browser context that holds cookies
the client registration and redirect URI
the user account that receives the authorization result
The email fixture adds another boundary.…