HOW RECUS WORKS
Routes & page exploration
Route paging is how Recus moves beyond the starting page. It does not blindly test every link: each newly reached destination is considered before it gets its own test plan.
From a navigation to a new page
Record the destination
When an interaction reaches a new URL, Recus records the route and the test or control that led there. An observed route is not yet a tested page.
Check scope and repetition
Automatic page exploration stays on the starting hostname and avoids revisiting equivalent routes. Other domains and sibling subdomains are not automatically added as pages to crawl. Explicit ports must also match; an HTTP-to-HTTPS upgrade can remain in scope.
Consider meaningful URL differences
Different URLs can represent the same page pattern. Recus considers whether query parameters change the page’s behavior and groups repetitive destinations to avoid spending the run on near-identical screens.
Choose the starting session
A destination may need session context captured earlier in the journey. Recus considers relevant cookies and browser storage, then chooses whether to reuse that context or open a clean view.
Preview and prioritize
Recus previews eligible destinations and considers their importance to the product journey. Repetitive, low-priority, unavailable, or unsuitable destinations may not receive a full suite.
Study and test selected pages
Approved destinations join the page queue. Each selected page gets a fresh study and test plan, and can reveal further controls or routes while the run’s limits allow.
Pagination, filters, and repeated pages
A Next page control or filter can expose another URL or change the current UI. Recus considers the observed change; it does not promise to visit every numbered page, record, or filter combination. URL changes that meaningfully affect behavior may deserve separate coverage, while repeated page patterns may be grouped.
For example, opening a billing settings screen may add a distinct user journey. Visiting many records with the same detail layout may add much less. These are coverage decisions, not proof that the omitted pages are correct.
Why a route may remain untested
- Outside scope or unsuitable to preview
- A route may leave the starting site or appear to trigger an action such as signing out or deleting something. Route filtering is not a guarantee that all interactions are side-effect free.
- Repeated or lower priority
- Recus may already have considered an equivalent destination or enough of the same page pattern.
- Unavailable context or decision
- The page may not load, its required session may not be reproducible, or the page-selection decision may be unavailable.
- Run limits reached
- Page and navigation budgets bound exploration. Remaining destinations do not become passes when the budget runs out.
Seen, selected, and tested are different