HOW RECUS WORKS
How Recus works
One URL starts a sequence of observations, decisions, and browser checks. Here is what happens at each stage, in plain English.
The scan, step by step
Open the starting page
Recus opens the URL in a browser. The page must be reachable from the scan environment. An inaccessible page or a login barrier can limit what the run can explore.
Understand what is on screen
Recus studies the page’s appearance, accessible labels, controls, and structure. It forms a working description of what the page is for and what a user might do there.
Draft a first-pass test plan
The observed interface becomes a set of focused checks, each with actions and an expected outcome. These expectations are inferred from the page, not a replacement for your product requirements.
Decide whether skills are needed
For each relevant test, Recus checks whether it needs a capability beyond browser interaction, such as receiving a verification email. A supported plan can combine skill actions with browser steps.
Execute and collect evidence
Recus performs the planned actions, records what happened, and compares the observed outcome with the expectation. Tests use separate browser contexts, with relevant starting session state when available.
Explore newly revealed controls
A menu, dialog, or next form step may appear during a test. Recus records how it was reached and considers useful follow-up tests that can reproduce that journey.
Consider newly reached pages
A navigation can reveal another route. Recus checks scope, repetition, session needs, and page importance before adding it to the run. Selected pages repeat the study-and-test cycle.
Bring the evidence back for review
The report brings together findings, available visual evidence, actions, and route context. Your team reviews uncertain results and decides what needs fixing or deeper testing.
Two kinds of discovery
- New UI on the current page
- Opening a menu reveals its options. That is element discovery: the follow-up belongs to the current page and needs the actions that opened the menu.
- A different page
- Following a settings link reaches a different URL. That is route discovery: the destination is considered for its own page study and test plan.
Why a scan is not an exhaustive audit
Discovery and page visits have limits. A repeated screen, inaccessible route, missing capability, unavailable decision, or exhausted run budget can leave part of a journey untested. A finished run means the run has ended—not that every possible state was checked.
Use a test environment