guard-e2e-test

To generate end-to-end guard tests, run agent-browser to explore your running web application and automatically produce Playwright-based specs that validate cross-page journeys like signup, dashboard, and logout. This verifies state persistence and authentication flows before writing tests.

Automated guard testing traverses multi-route web app journeys, such as login to protected routes, to verify state persistence, authentication flows, and proper redirects. It prevents regressions in complex flows by validating branch behavior and data-state invariants across cross-page transitions.

Agent-browser exploration guides automated discovery of a running web application to map multi-route journeys before test generation. This mandatory exploration phase ensures generated Playwright tests use strict data-testid locators and per-journey naming conventions to validate authentication and redirects.

Yes, guard-e2e-test validates state persistence across route transitions by checking auth tokens, session data, and local storage. It ensures unauthenticated access redirects properly and data-state invariants hold across branches during multi-route journeys.

The best way to structure Playwright tests for cross-page journeys is placing them under a guard directory with per-journey naming conventions. This approach uses strict data-testid locators to validate multi-route flows like signup, dashboard, and logout consistently.

Yes, automated journey testing requires strict data-testid locators to reliably identify elements across multi-route web app journeys. This ensures generated Playwright specs accurately validate state persistence, authentication flows, and proper redirects without fragile selectors.