HOW RECUS WORKS
Element discovery
Not every control is visible when a page first loads. Recus looks at the initial interface and at the new UI that appears while tests are running.
Start with the visible interface
Inputs, buttons, links, tabs, and other interactive controls provide the starting points for tests. Recus uses visual and accessible context to understand what each control appears to do. Custom widgets, missing labels, and inaccessible states can make discovery incomplete.
Follow the reveal path
Notice a new control
A test opens a dialog, expands a dropdown, or advances a form. Recus records the newly exposed controls along with the interaction that revealed them.
Keep the journey, not just the destination
A Save button inside a dialog is not available on a fresh page. Its follow-up test must first open the dialog. A later wizard step may require several earlier actions.
Draft a reproducible follow-up
Recus considers the earlier test, its outcome, the reveal path, and the available starting state. The follow-up needs a way to reach the new behavior from its own browser context.
Check whether the test adds value
Before running, Recus checks whether the candidate covers a new behavior, has a supported expectation, and is executable with the available inputs and capabilities.
Continue within the discovery limit
An accepted follow-up can reveal more controls. Those become candidates for another round. Repeated discoveries are filtered and the number of rounds is bounded.
Why a follow-up may be skipped
- Duplicate or low-value coverage
- Another test already covers the behavior, or the candidate adds little useful coverage.
- Unsupported journey
- The required setup, input, or capability is not available, so the test cannot reliably reproduce the revealed state.
- Unproven expectation
- The candidate assumes a product requirement that the available evidence does not establish.
- Decision unavailable
- If Recus cannot complete the follow-up review, it does not automatically admit the candidate as a valid test.
Example: a two-step signup form
The first test submits the signup form and reveals a verification screen. Recus does not simply open the starting URL and search for a verification field. It considers how to recreate the signup journey, including a fresh inbox if needed, before drafting a follow-up for the new screen.
If that journey needs a capability Recus does not have, seeing the verification screen once does not make it independently testable.
Discovered does not mean tested