browser-testing-stos

What problem does it solve?

Browser automation processes often proceed after failures, creating flaky tests and undetected issues. This skill enforces a blocking STO workflow that halts on verification failure and requires fixes before continuing.

Core Features & Use Cases

• Structured, step-by-step verification with a transactional flow: CHECK → VERIFY → COMPARE → DECIDE → FIX → RE-VERIFY → PASS → NEXT.
• UI vs code alignment: UI behavior is always compared to route definitions, authorization guards, and backend permissions; when differences exist, code wins and UI is updated.
• End-to-end browser testing coverage: authentication context, navigation, CRUD actions, and security boundaries across modules, with evidence capture and regression checks.

Quick Start

Initiate an STO-based browser test by selecting a target app and following the CHECK → VERIFY → COMPARE → DECIDE → FIX → RE-VERIFY → PASS → NEXT sequence for each module, capturing evidence at every step.