Skill in Engineering
aegis-ui-test
Drive the project's own web app in a real browser to verify a UI change actually works, and fix what is broken before calling it done. Not a report generator - it fixes and re-verifies in the same pass.
Acceptance verification against a running environment, not against a diff and not against a test suite. A component suite can be green while the page is blank, the click does nothing, or the console is full of errors - those failures are only visible once something real is rendered and clicked. Drives the app through the `browser` provider family, reads the console as well as the screen, and when it finds something broken it fixes it and re-verifies in the same pass rather than reporting it. Where no browser backend is reachable it says so plainly instead of passing on the strength of a green build.
- Modes
verify- Audience
dev- Depends on
aegis-context- Providers
browser:navigatebrowser:snapshotbrowser:screenshotbrowser:clickbrowser:typebrowser:fill_formbrowser:press_keybrowser:evaluatebrowser:console_messagesbrowser:network_requestsbrowser:wait_forbrowser:handle_dialog- Knowledge
_shared/code-review-gates.md