Automated test automation for web apps
Use ego(lite) with Codex or Claude Code to turn a plain-English test brief into real test automation. Your agent opens your app in a real browser, follows the flow you specify, records what happened, and gives you a clear result you can review — without taking over the tabs you are using.
Use this four-step test automation process for a local, staging, or production-safe web app you are authorized to test. Describe the browser flow in plain English, including the starting state, actions, assertions, test data, and stop conditions. The agent works in a separate browser Space, so you can watch a run, take over when a human decision is required, and keep your normal tabs clear.
Download ego(lite), then choose the browser context you want to use. For tests with real side effects, point the agent at localhost, a test account, or a staging environment — the same safety boundary you would use for a manual check.
Tell the agent which URL to open, the user journey to follow, the data or account it may use, and what success looks like. A precise brief can cover a login flow, form validation, cart, checkout sandbox, search, dashboard, or any other repeatable browser task. Name visible labels and outcomes instead of tying the brief to fragile CSS selectors; the agent can inspect the rendered page and ask when the intent is ambiguous.
The agent opens the app in its own ego(lite) Space and performs the test automation steps in a real browser. You can inspect the rendered page, console state, and progress while the test runs, without losing the tabs you were already using. For visual smoke checks, ask it to verify the visible control, text, or layout region rather than hard-coding a selector that changes with every redesign.
Ask for a concise report with the route tested, steps completed, expected versus actual result, screenshots or source references where useful, and a clear failure point. Save the prompt and report as the test case, then send the same test automation prompt again after a fix or before a merge instead of relying on memory.
ego(lite) gives your coding agent a real, visible browser for software automated testing. Instead of a black-box test runner, you get separate Spaces, an observable test path, and an outcome that tells you what actually happened on the page.
Every browser step adds to the time between your test brief and the result. Across our 31-task benchmark on live sites, ego(lite) averaged 398 seconds per task against 605 for agent-browser, 52% faster. Actual time varies by website, workflow, and network conditions.
Use a separate Space for each feature, account role, viewport, or regression scenario. Test automation stays organized instead of mixing state across a pile of browser tabs, and you can return to the exact Space where a run stopped.
Open any Space to see the current page and the step the agent is trying to complete. If a workflow reaches MFA, a payment confirmation, a destructive action, or another decision that should stay human, take over the browser and decide what happens next.
Reuse a browser context you choose for roles or test accounts that need a signed-in flow, rather than handing credentials to a test-automation service. Your app's access controls, MFA, rate limits, and permission checks remain in effect; ego(lite) does not bypass them.
For agency or freelance work, keep one test brief per client and run it against each authorized staging URL in its own Space. Record the site, account role, browser version, and fixture in every report so a broken form or checkout failure is attributable instead of being mixed into one generic pass rate.
When a test fails, ask the agent to capture the URL, screenshot, console error, network status, and the element or text it expected. It can suggest a more stable locator or a changed step, but keep the proposed change under review and rerun the original assertion; automatic selector healing can hide a real regression if the expected behavior changed.
Point the agent at a local preview or staging deployment for a targeted pre-merge smoke test. Return a blocked result when the environment, fixture, MFA, or permission is unavailable; do not make a green-looking report by skipping a failed check. Keep deterministic unit, integration, accessibility, and security suites in CI alongside the browser run.
ego(lite) helps an agent execute the test procedure you define in a browser context you authorize. It can inspect a web flow and report its outcome, but it does not make an unsafe test safe, infer a product requirement you did not state, or bypass your app's access controls.
Repeatable web application paths you authorize it to open and inspect.
Unsafe, irreversible, private, or ambiguous actions remain under your control.
Start with one safe user journey, state the expected result, and let Codex or Claude Code execute it in an observable ego(lite) browser Space. You get a test result you can inspect, rerun after a fix, and turn into a more reliable release habit.