AegisRunner documentation
Explore your app, generate tests, investigate failures, and automate regression testing.
AegisRunner explores websites and mobile apps, generates tests from the pages and screens it reaches, and helps you investigate failures with evidence.
Start with a scan to discover your app. Review the generated tests, then run them again after changes or from your deployment pipeline.
Run your first scan
Start with a website URL and review the pages AegisRunner reaches.Test behind a login
Add test accounts, session cookies, or a custom sign-in flow.Test a mobile app
Upload an Android or iOS test build and explore its screens.Automate your tests
Run suites in CI and collect JUnit results.Understand the workflow
| Term | What it means |
|---|---|
| Project | The home for an app's scans, logins, tests, runs, and settings. |
| Scan | Exploration of a website or mobile app, followed by test generation. |
| Suite | A collection of test cases, often associated with a page or workflow. |
| Test case | A sequence of actions and checks for expected behavior. |
| Run | An execution of existing tests, with a result for each case. |
| Baseline | A saved reference used to compare later results or screenshots. |
A completed scan does not mean every generated test passed in a later run. Use Overview for discovery results and Runs for execution results.