HOW RECUS WORKS
Test planning & execution
A test is a small, explainable journey: what to try, what should happen, and what actually happened. The generated plan is a first pass for your team to review.
Draft checks from the page
Recus uses the page context and controls to propose focused checks. Depending on the interface, these may cover a happy path, required fields, invalid formats, boundaries, keyboard interaction, or visible feedback. Not every category applies to every page.
Each test has a purpose, a sequence of actions, and an expected outcome. A generated security-related check is not a penetration test or a security certification.
Prepare, run, and observe
Check requirements
Recus considers whether the plan needs a skill or human-provided input. If a skill fully covers the relevant requirements, the plan can be updated to use it.
Start from a defined state
Tests run in separate browser contexts. Applicable cookies or browser storage may be supplied as starting session context, but an open menu or another test’s live page is not automatically inherited.
Perform the actions
Recus interacts with the browser using actions such as clicking, filling, selecting, and scrolling. Skill actions can supply information for later browser steps, such as an email code.
Collect evidence and assess
Available screenshots, recordings, traces, action history, and browser observations help explain the result. An execution problem or missing artifact may limit what can be concluded.
Feed discoveries back into the run
New controls become follow-up candidates. Newly reached URLs become route candidates. Both need further decisions before they count as additional coverage.
Review the expectation as well as the result
Suppose a test expects a form to reject a phone number containing spaces. Your product may intentionally allow spaces. The browser evidence can be accurate while the generated expectation is wrong. Review both before treating a finding as a bug.
Separate browser contexts reduce carry-over in the browser, but they do not undo records created on your server. Use disposable data and review any test-created accounts or submissions in your environment.
A completed action is not proof of the whole flow