// human-like testing, automated
Test your web or mobile app without writing tests.
AegisRunner signs in, explores real workflows, writes and reviews the tests, and shows you what broke with page-level evidence you can act on.
// wcag evidence reports
Report on the public and signed-in pages you actually examined.
Generate a printable WCAG 2.2 A/AA evidence report from a completed scan. It records authenticated coverage, reproducible sampling, detected failures, exclusions, and the manual review still required.
// one run, useful output
A report your whole team can use.
Start with the app. Leave with the failures, the evidence, and the tests that keep those workflows covered.
Issues grouped by page
Functional failures, broken links, visual defects, and audit findings stay together under the page where they happened. Open one page and see its complete story.
Replayable user-flow tests
Login, search, checkout, account changes, and multi-step journeys become readable test cases with grounded assertions and resilient locators.
Audits in the same run
Accessibility, SEO, security headers, performance, API behavior, and visual changes are checked alongside the functional workflow.
// a second set of eyes
Human-like coverage without a black-box answer.
AegisRunner does more than ask one model for a test list. It separates exploration, authorship, review, and runtime evidence so a confident answer has a traceable reason.
See the full testing process- 01Explore what is actually there
A real browser maps reachable pages, controls, forms, and authenticated workflows instead of guessing from source code or a prompt.
- 02Write tests from observations
The authoring model turns discovered behavior into positive, negative, boundary, and multi-step cases tied to the controls it saw.
- 03Review with a second model
An independent reviewer checks depth and missing controls, then adds coverage without silently replacing the original generation record.
- 04Replay before you trust it
Eligible cases run against the app. Runtime outcomes retain whether the author or reviewer created the case, so quality can be measured rather than assumed.
// one journey, every surface
Test web and mobile together, not as separate products.
Act in a native app on a real device, then verify the result in the browser within the same journey. Catch the synchronization failures that a web-only or mobile-only suite cannot see.
- Place an order in the app and verify it in the web dashboard.
- Change status on the web and confirm the mobile customer sees it.
- Run native Android and iOS coverage alongside browser workflows.
Cross-surface test coverage
AegisRunner runs a single automated test across a customer's mobile app (Android and iOS) and the web (admin console and customer portal), verifying every action end to end:
- customer places an order in the app → admin sees it in the dashboard
- admin ships the order on the web → customer sees the update in the app
- admin resolves a request → customer sees it on the web portal
- customer submits a request on the web → admin sees it in the queue
- order placed in the app → shows in the customer's web account
- customer updates their web account → reflected in the app
- the same customer journey on both phones → all green
- customer orders on iPhone → admin sees it in the dashboard
- order placed on iPhone → shows in the customer's web account
// cloud, local, or private
Start in the browser. Bring it into your workflow when ready.
Scan a public URL with no setup, run a local browser against localhost, or place a self-hosted runner inside a private network. Generated Playwright and JUnit output fit the tools your team already uses.
# test localhost with a browser on your machine
$ aegis scan --local --url http://localhost:3000
# run a generated suite in CI
$ aegis run --format junit --output results.xml
# or trigger a hosted scan from any pipeline
$ aegis scan --url https://staging.example.com// common questions
What teams ask before the first run.
Do I need to write test code?
No. Start with a website URL or a mobile build. AegisRunner explores the product, creates the test cases, and runs them. Pro and Business plans can export generated web suites as Playwright TypeScript.
Can it test pages behind a login?
Yes. Add the login once and AegisRunner can explore authenticated dashboards, account settings, checkout, and other private workflows. Login recovery is handled during longer scans too.
How are AI-generated tests checked?
One model authors the cases, a separate reviewer looks for missing controls and shallow coverage, and eligible cases are replayed in a real browser. Results stay tied to the page and evidence that produced them.
Will a scan change data in my app?
You control whether testing may submit forms or perform write actions. Mutation-capable testing requires explicit project authorization; otherwise the execution fence blocks unsafe requests.
Does it test mobile apps?
Yes. Upload an Android or iOS build to test it on real devices. AegisRunner can also run one journey across mobile and web, such as placing an order in the app and verifying it in the web dashboard.
What do I get after a run?
You get page-grouped issues, generated functional tests, screenshots and evidence, plus accessibility, SEO, security, performance, API, and visual checks where applicable.
Can it run in CI or against localhost?
Yes. Use the CLI for localhost and private-network testing, run suites from CI with JUnit output, or use the Vite, Nuxt, and Next plugins from your development server.
// start with the product you have
Run a website check now. Add deeper testing when you are ready.
The public website scan needs no account. Create a free workspace for authenticated testing, mobile builds, saved baselines, and CI runs.
Already using AegisRunner? Sign in directly