---
title: "Verify remember-me applies the documented session duration"
description: "Compare ordinary and remembered sign-in with controlled session inspection and expiry fixtures instead of inferring persistence from checkbox appearance."
canonical_url: "https://vostride.com/agent-library/authentication/remember-me-duration.md"
md_url: "https://vostride.com/agent-library/authentication/remember-me-duration.md"
content_kind: "recipe"
topic: "authentication"
---

# Verify remember-me applies the documented session duration

Compare ordinary and remembered sign-in with controlled session inspection and expiry fixtures instead of inferring persistence from checkbox appearance.

## Risk

Remember-me settings often affect server expiry and browser storage differently. The useful contract is the application documented duration and reopening behavior, which must be verified with controlled clocks or supported session fixtures.

## Fixtures

- Two disposable accounts with identical permissions and no prior remembered sessions.
- A documented duration policy for ordinary and remembered sessions, including idle versus absolute expiry.
- Application hooks that inspect expiry metadata and advance or expire test sessions without changing a shared production clock.

## Steps

1. Sign in with the ordinary account while leaving remember-me unchecked; verify its account identity and inspect its session expiry metadata.
2. Sign out, then sign in with the second account after explicitly selecting remember-me; verify that account identity and inspect its expiry metadata.
3. Compare both reported durations with the documented policy, accounting for a stated tolerance around the login timestamp.
4. Use the supported fixture to place each session beyond the ordinary expiry but within the remembered expiry; open the private page for each in separately executed account runs.
5. Verify the ordinary session requires sign-in while the remembered session remains valid, then inspect their server session states.

## Expected results

- The remember-me choice changes only the session properties promised by the product.
- The ordinary session loses access at the controlled expiry boundary.
- The remembered account remains the same identity and follows its distinct documented expiry policy.

## False-pass traps

- The checked checkbox proves user input, not a persisted session policy.
- A browser kept open indefinitely cannot establish behavior promised specifically for browser restart.

## Cleanup

- Revoke both disposable accounts sessions and reset any per-account clock fixture overrides.

## Use with agent-qa

Adapt this test design to your application's acceptance criteria and configured target using the [recipe execution guide](/agent-library/software-factory/turn-a-recipe-into-an-agent-qa-test.md). External fixture setup and non-UI checks require your own supported hooks or test tooling. Validate the authored test, execute it, and inspect the completed evidence; this recipe is not a recorded test result.

## References

- [agent-qa test](/docs/agent-qa/configuration/test.md)
- [agent-qa hooks](/docs/agent-qa/guides/hooks.md)
- [agent-qa auth state](/docs/agent-qa/guides/auth-state.md)

- [Authentication QA recipes](/agent-library/authentication.md)
- [Software factory QA library](/agent-library.md)