browser-testing-stos

To stop browser automation after a verification failure, you need a blocking workflow that halts execution immediately. This skill applies a structured task orchestration flow that prevents progression until the failed step is fixed and re-verified.

The best way to verify UI behavior against backend permissions is to compare UI actions directly with route definitions and authorization guards. This skill enforces a comparison step where code wins and the UI is updated when differences exist.

To automate CRUD testing and navigation audits step by step, follow a transactional sequence: CHECK, VERIFY, COMPARE, DECIDE, FIX, RE-VERIFY, PASS, and NEXT. This ensures each module is systematically validated with evidence capture before moving forward.

Automated browser tests become flaky when processes proceed after failures, leaving issues undetected. You can prevent this by applying strict gating and re-verification loops that block progression until all checks pass and evidence is collected.

Yes, this browser testing approach works for auditing security boundaries across modules. It systematically tests authentication context, navigation, and CRUD actions while capturing evidence to ensure strict alignment with backend authorization guards.