← Back to wkappbot-workflow
wkappbot-workflow
★★★
wktool QA pattern: token-efficient bug detection scripts
How to write wkask/wkcdp-style QA scripts that find bugs cheaply. Key principle: state-check first (fast), eval-js second (medium), DOM check last (slow). Auto-file suggest on confirmed bugs.
user/developer
wkcdpwkaskqacookiedetectpatternscripteval-js
Steps
- PRINCIPLE: wk-tool scripts replace Claude po...
- STATE-CHECK FIRST (cheapest): before any CDP...
- MINIMIZED RECOVERY (before eval): if Chrome...
- EVAL-JS (medium cost): use 'wkappbot a11y ev...
- CROSS-VALIDATE heuristics: if you have a fas...
- AUTO-SUGGEST on confirmed bugs: if off-scree...
- TIMING: cookie/DOM checks at session CLOSE (...
- NAMING: wk<domain>.ps1 in D:/GitHub/WKAppBot...
- TEST SUBCOMMAND: every wk-tool should have a...
- USER-PERSPECTIVE BASELINE: for public SDK re...
- TOKEN-SAVING WAITING: while a smoke test is...
- FASTEST VALID SMOKE FIRST: always look for t...