SKILLS
How skills are selected
Skills add capabilities beyond normal browser actions. Selection happens for a specific test and its journey—not just because a page contains a familiar word like “email.”
The decision, step by step
Read the test’s actual goal
Recus considers the expected outcome, planned actions, page context, and any earlier steps needed to reach the test’s starting point.
Look for a relevant available skill
If the test may need something beyond browser interaction, Recus considers the capabilities of relevant enabled skills. An ordinary field-validation test can remain browser-only.
Check the whole requirement
Selecting a useful skill is not enough. Recus checks which requirements it covers, which remain uncovered, and whether necessary inputs are missing or unsuitable.
Prepare a supported plan
Only a fully covered decision allows the test to be rewritten with skill actions. The revised steps must be valid before execution. Partial support does not cause Recus to invent the missing capability.
Execute and judge separately
The skill runs as part of the test. Its actions and results contribute evidence, but the browser journey and expected outcome still need assessment.
What the coverage labels mean
- Full skill coverage
- At least one skill is selected, with no identified uncovered requirements or input issues. The test can be prepared with skill actions. This describes capability coverage, not a passing result.
- Partial skill coverage
- A skill is relevant, but some requirements or inputs remain unresolved. Recus does not regenerate the test as a fully supported skill-assisted plan.
- No skill / skills unavailable
- No skill was selected. The test might simply need browser actions, or a required capability might be unavailable. Read any listed missing requirements rather than treating these cases as equivalent.
Three examples
- Reject a malformed email address
- Typing an invalid address and checking the error is a browser test. It does not require an inbox.
- Create an account and verify its email
- A fresh inbox and access to its verification message can make Email relevant. The test still needs to demonstrate that the application reaches the expected verified state.
- Verify email and then receive an SMS code
- Email can cover the inbox portion, but the current skill catalog does not provide SMS reception. That is not complete skill coverage.
When a capability is missing
Where a decision records an uncovered requirement, browser-only success must not be treated as proof of the entire expected outcome. Recus can report a warning explaining what remains unverified.
A skill-planning or execution error is also not evidence that your application passed or failed. Inspect the recorded reason and decide whether to supply appropriate test input, rerun, or verify the remaining part manually.
Capability coverage is not test coverage