Product model

Core Concepts

The pieces Recus uses to turn one URL into a reviewable first pass of QA coverage.

Recus works with your tester

The agent handles the mechanical sweep and brings back evidence. A person reviews the findings, corrects assumptions, extends the important paths, and decides what ships.

The scan model

text

Starting URL
  ↓
Page context + product brief
  ↓
Elements → first-pass test cases
  ↓
Fresh Chromium tabs + evidence
  ↓
Discoveries → reveal paths → same-origin crawl
  ↓
Pass / fail / warning → human review → report

Building blocks

Scan

One run against one starting URL. A scan contains the page study, generated test cases, browser execution, discoveries, crawl results, evidence, and final report.

Page context and product brief

Before interacting, Recus combines a full-page visual read with the accessibility tree. It writes a short brief describing what the page appears to do, who it serves, and what successful behavior should look like.

Element

An interactable control found through vision and accessibility data: inputs, buttons, links, tabs, menus, and controls revealed below the fold. Each element keeps its accessible name and locator context.

Test case

A generated check against one element or behavior. Recus drafts happy paths, empty submits, invalid formats, boundaries, security probes, keyboard checks, and UX assertions for your team to review and extend.

Discovery and reveal path

Interactions can expose new UI such as dialogs, menus, and extra form steps. Recus records the exact actions that revealed each element, then replays that path before testing it.

Crawl

A cycle-safe, breadth-first traversal of same-origin routes found during testing. Each discovered page gets its own context and first-pass suite. The default crawl limit is eight pages.

Verdict

A pass, fail, or warning produced from the visual result, action log, and browser state. The verdict is a recommendation backed by evidence; your reviewer makes the final call.

Report

The shareable artifact from a scan: findings, before-and-after screenshots, video, Playwright traces, action logs, discovered routes, explanations, and suggested fixes.

Human in the loop

When a test reaches a login wall, OTP, CAPTCHA, or decision it should not make alone, Recus pauses and asks. After you answer, it re-runs only the blocked test instead of restarting the scan.

How to read a verdict

Pass

Observed behavior matched the generated expectation.

Fail

Evidence suggests a functional, validation, or security defect.

Warning

The flow worked, but usability, clarity, or accessibility needs review.

Treat the report as a first pass

Generated coverage is a starting point, not a release decision. Review the evidence, dismiss false positives, and add the product-specific scenarios only your team knows.