Turn the recorded login into an explicit outcome
Start URL: https://app.example.com/login Preparation: supply the disposable QA account's email and password. Enter the email in the recorded Email field. Enter the password in the recorded Password field. Click the recorded Sign in button. Assert that the account menu is visible on the dashboard. Assert that Recent activity is visible. Assert that no sign-in error is visible.
Illustrative Reflect recorded step list. This is not an export format or API payload. The example account uses password login without an authenticator challenge. Source 1 · checked 2026-10-23. Source 2 · checked 2026-10-23.
Name: Account dashboard access Starting path: /login Environment: Staging Instructions: Sign in with the saved QA login and open the account dashboard. Expected: The account menu and recent activity are visible. A sign-in error or unresolved login challenge does not pass.
Store the email and password in an environment login. When the sign-in challenge itself is under test, select Start logged out under Options, or leave Reuse login sessions off on the login. Session reuse is off by default. If your real account needs an authenticator code, save its setup key and describe that challenge too. The benchmark below demonstrates a blocked prerequisite, not successful authentication.
The run ended with an Error status, which our benchmark scores as cannot verify: the security check failed and no credentials were supplied. It illustrates an unresolved login prerequisite, not a successful sign-in or proof that your authentication will work.