Test a Mac app Three levels, cheapest first. Each new story gets the cheapest level that can prove its acceptance criteria. A bug fix starts with a test that fails. | Level | Proves | Speed | | --- | --- | --- | | Unit tests (Swift Testing) | Rules, parsing, data | Seconds | | Self-test ( ) | The app's real functions on a test store | Seconds | | Key events and menu audit (inside the self-test) | Keyboard flows and every shortcut, without the screen | Seconds | | Debug bridge + computer use | Global shortcuts, panels, permissions, other apps | Minutes | Snapshots ( skill) prove how it looks.…