web-testing

Validate web applications using a layered strategy that checks integration, end-to-end journeys, accessibility, performance, and security directly against running systems, organizing outputs into evidence directories to prevent false positives from mocks.

Test Core Web Vitals and WCAG compliance by applying the performance and accessibility validation layers to new page routes, collecting real browser outputs and system evidence to verify feature-level quality.

Yes, you can use Playwright for browser automation as the strategy delegates browser flows to playwright-validation, complementing visual-inspection and verdict-writer agents to review and enforce live-system checks.

The best way to structure evidence is producing organized e2e-evidence directories for each validation layer, ensuring verdicts cite real command and browser outputs directly from running web applications.

Yes, this approach works for validating form input sanitization and sign-up or login journeys by enforcing live-system checks across user journeys and APIs without relying on mocked responses.

You should not use mocks when a practical, real-system validation strategy is required, as mocks prevent false positives by verifying integration, end-to-end, accessibility, performance, and security directly against running applications.