01
Study
input[email]
button[Continue]
a[Forgot password?]
43 interactable elements found
Recus scrolls to load lazy content, reads the accessibility tree, and writes a product brief before touching anything.
QA that learns
how your product works.
Recus learns your product, tests important workflows in a real browser, and reports reproducible bugs with evidence—without dozens of test scripts to maintain.
From product understanding to reproducible bugs
DiscoveryRoutesEmail skillHuman inputEvidenceSlack
ExecutionReal browser
DiscoveryRevealed UI
Current skillEmail
When neededHuman input
Report deliverySlack
30-second product tour
One URL in. Reproducible bugs out.
A recorded tour from a URL to browser-tested findings. The reel illustrates the workflow; actual run duration, coverage, and results vary.
Recus / Product reel
00:30 · Silent00:05
Reads the page
00:12
Writes the tests
00:19
Clicks for real
00:26
Returns proof
Illustrative product demo
Follow a sample scan, end to end.
Pick a sample app and explore the study, execution, and review stages. This recorded illustration uses sample data; it is not a live run.
02
Run
✓ email input — invalid format rejected
✓ email input — XSS probe sanitized
✗ phone field — accepted abc
? submit button — no visible feedback
Pass 35Fail 3Warn 5
Every test runs in a fresh browser tab with video and a Playwright trace.
03
Review
Phone field accepts letters
HighThe phone input accepted alphabetic characters and advanced without an inline validation message.
Suggested fix
Validate the normalized phone value before submit and attach the error message to the field with aria-describedby.
You review, correct, and decide what ships.
Important workflows, tested.
Reproducible bugs, reported.
Point Recus at staging, a preview deploy, or production. It learns the interface, exercises the workflows that matter, and returns the steps and evidence your team needs to reproduce every finding.
01 / 09
Page understanding
Not a replacement
More workflow coverage. Less test-script maintenance.
First look, like a person
Recus reads the page and accessible controls, including content exposed by scrolling, before turning that context into a test plan.
Focused first-pass checks
Explore required fields, empty submissions, invalid formats, boundaries, happy paths, and UI behavior. The plan reflects the page, not a guarantee of exhaustive coverage.
Acts, then watches
Browser actions can reveal dialogs, new form steps, and useful destinations. Recus considers discoveries and preserves the path that exposed them.
Skills when the test needs them
The Email skill can supply an inbox and its verification message. An email-format validation check may only need browser actions.
Asks when it should
Supported input can unblock the affected test. CAPTCHA and reCAPTCHA may still need manual review; skipped or unverified work is not presented as a pass.
Discovery & crawl
Finds what clicks reveal. Follows where links go.
Recus looks beyond the first screen, considers follow-up checks for revealed UI, and selects useful routes for further testing. Discovery expands the plan without claiming complete coverage.
01
Understand the starting page
Recus combines the visible interface, accessible controls, and page context. Scrolling helps expose below-fold or lazy-loaded content.
02
Notice what actions reveal
A menu, dialog, or new form step can introduce more controls. Recus records useful discoveries with the path that revealed them.
03
Consider follow-up checks
Useful new controls can lead to follow-up tests that replay the reveal path first. A discovery is not itself proof that a check ran or passed.
04
Select useful routes
Destinations are assessed for scope, repetition, session requirements, importance, and run limits. Selected pages get their own study and tests; not every link is crawled.
Pipeline
Five steps from paste to report.
01
Study the page
Observepage context
Read the interface, accessible controls, and visual context—including what scrolling reveals—to understand what the page does.
https://your-app.com/checkout
Run
02
Plan the checks
Plantests and skill decisions
Generate useful checks and decide whether browser actions are enough. Use the Email skill when a journey needs a fresh inbox or verification message.
discovering elements...
button[Submit] · input[email] · a[Forgot?]
running test suite (43 tests)
PASS 35 · FAIL 3 · WARN 5
03
Run and discover
Executebrowser actions
Interact in a real browser. Remember controls revealed by actions and consider follow-ups. Selected same-host routes get a new study and test plan.
discovering elements...
button[Submit] · input[email] · a[Forgot?]
running test suite (43 tests)
PASS 35 · FAIL 3 · WARN 5
04
Ask and assess
Reviewpass / fail / warning
Request human input when supported or leave a blocked check unverified. Compare expected behavior with the observed result and available evidence.
Before / After
Phone field accepted "abc"
05
Report and share
Sharereports and Slack
Review results in the report. With Slack connected and a channel selected, send a completed-run summary manually or enable completion notifications.
input[email]3 tests pass
input[phone]3 tests fail
button[submit]2 tests pass
a[forgot]1 test warn
Workflow
Learn the product. Test the workflows. Report the evidence.
Illustrative previews with sample data—not live run results.
01
Start with a URL
Choose a reachable web app you own or have permission to test. Start from the dashboard without writing a test suite first.
https://your-app.com/checkout
Run
02
Follow the run
See the run progress as Recus studies the page, plans checks, and interacts with the browser.
discovering elements...
button[Submit] · input[email] · a[Forgot?]
running test suite (43 tests)
PASS 35 · FAIL 3 · WARN 5
03
Triage with evidence
Compare expected behavior with the observed outcome and the screenshots, recordings, traces, and action logs available for that run.
Before / After
Phone field accepted "abc"
04
Answer when it asks
Supply appropriate test information for supported human-input requests, or skip the affected check. CAPTCHA barriers may remain unverified and need manual review.
Human input requested
This check needs authorized test information.
Continue when supported · or skip as unverified
05
Audit the coverage
Review discovered elements and selected routes alongside outcomes. A discovered control or URL is not automatically a completed test.
input[email]3 tests pass
input[phone]3 tests fail
button[submit]2 tests pass
a[forgot]1 test warn
06
Bring results to Slack
Connect your workspace, choose a channel, and send completed-run summaries manually or automatically. Delivery errors do not turn a valid QA run into a failed run.
R
Recus Bot
🐛 3 bugs found on /checkout — View report
Understands the page
Visual and accessible context help Recus find meaningful controls, including below-fold content.
Follows new states
Revealed UI and selected routes extend the first pass, while skills and human input support journeys that need more than browser actions.
Explains the result
Review the expectation, actions, and outcome with available evidence. Connected Slack delivery brings a completed-run summary to the team.
Discovery
Context
before actions
Understand the page and what interactions reveal.
Email skill
Inbox
when required
Continue verification journeys beyond the browser.
Human review
Control
when input is missing
Supported input, explicit skips, and visible limits.
Slack
Summary
after completion
Results, top findings, and a report link.
Enterprise
Reports, history, and control at scale.
01
Reachable, authorized targets
Start with a web app you own or have permission to test. Access requirements and session state affect the coverage available.
02
Reviewable run history
Return to completed runs and their available evidence. Report access remains subject to permissions.
03
Human input and test data
Provide appropriate test information for supported requests. Do not assume an access or verification barrier was automatically cleared.
04
Connected Slack delivery
Choose a channel Recus can access. Send a completed run manually or enable automatic completion summaries.
Illustrative findings
The kinds of issues a first pass can expose.
ILLUSTRATIVE FINDING
Phone field accepts letters
Impact: Invalid contact information can enter the workflow without clear validation.
ILLUSTRATIVE FINDING
Empty form submits
Impact: Required information may be missing from the next step.
ILLUSTRATIVE FINDING
No visible submission feedback
Impact: A user may retry without knowing whether the action succeeded.
ILLUSTRATIVE FINDING
Validation message stays below the fold
Impact: The user cannot see why a form will not continue.
ILLUSTRATIVE FINDING
Keyboard focus disappears in a dialog
Impact: Keyboard users may be unable to reach the next action.
ILLUSTRATIVE FINDING
Back navigation clears checkout state
Impact: A user may lose their progress when returning to an earlier step.
Who it's for
Sanity coverage for every kind of team.
Solo founders
Ship, paste the URL, read the report. A first-pass safety net when you're the only one testing.
Engineering teams
Run a first pass on a release candidate and review evidence before the next handoff.
Product & PM
Open the report, see the screenshots, file the bug. No eng translation layer.
Agencies
Scan every client site before handoff, then send the report as part of the deliverable.
QA engineers
You already know what to test. Recus gets you to the interesting part faster — it does the mechanical sweep, you bring the judgment.
Explore Recus
Choose the QA workflow you need.
Autonomous QA
See how Recus explores web apps and returns evidence-backed findings.
AI QA
Add an AI testing agent to your existing quality workflow.
AI testing
Move from a URL to generated checks and real browser execution.
Automated website testing
Validate functional flows across staging, previews, and production.
AI exploratory testing
Discover paths and edge cases that were never explicitly scripted.
Compare testing approaches
Compare Recus with Momentic, Playwright, Cypress, and BrowserStack.
Book a demo
Bring the release
you're worried about.
Get a tailored walkthrough of Recus using the kind of software your team actually ships—not a canned slide deck.
Book your demo →Tailored to your product · No sales theatre
What we'll cover
01
Test a real flow
Bring a staging URL or a release you care about. We’ll show how Recus explores it in a real browser.
02
Review the evidence
See how videos, screenshots, traces, and plain-language findings make failures fast to verify.
03
Map it to your process
We’ll shape the workflow around your team, release cadence, and current QA coverage.
Pricing
Start with a URL.
Review what it finds.
Start with a URL and review the evidence. See the pricing page for current access, available features, and run limits.
What's included
- ✓Selected route exploration
- ✓Progressive element discovery
- ✓Email skill for supported journeys
- ✓Evidence-backed reports
- ✓Available screenshots, recordings, and traces
- ✓Supported human-input requests
- ✓Connected Slack summaries
- ✓Run history
Let Recus learn your product.
Test important workflows in minutes and get reproducible bugs with evidence. No credit card or sprawling test suite required.
Product documentation