ui-test-testcafe
Use this skill when you need to design TestCafe UI automation with fixtures, selectors, roles, browser matrix execution, and reports; triggers include TestCafe UI testing, UI automation testing, and ui-test-testcafe.
How do I install this agent skill?
npx skills add https://github.com/naodeng/awesome-qa-skills --skill ui-test-testcafeIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill provides a comprehensive framework for TestCafe UI automation, including local execution scripts and automated validation of test artifacts. No malicious patterns, obfuscation, or data exfiltration attempts were found.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
TestCafe UI Testing (EN)
Chinese version: See the corresponding Chinese skill.
When to Use
- Need outputs that should land in a TestCafe UI testing workflow.
- The project already uses TestCafe or wants TestCafe-ready planning.
Output Format Options
Markdown by default unless the request explicitly asks for another format.
How to Use
- Open
prompts/ui-test-testcafe.mdand use it as the main prompt. - Add the real project context: scope, environment, constraints, risks, dependencies, and expected deliverable.
- If the input is incomplete, return a usable first version and mark missing information and assumptions.
Reference Files
-
When calibrating domain outcomes, valid controls, or evidence gaps, read references/domain-decision-example.md for sanitized input, per-item oracles, and reproducible calculations.
-
prompts/ui-test-testcafe.md: main prompt for this skill. -
references/framework-spec.md: tool-specific structure and coverage notes. -
references/setup-and-ci.md: setup, execution, and CI notes. -
examples/sample-context.md: sample request context. -
scripts/run-tests.sh: lightweight local execution entry point.
Domain Execution Essentials
- Confirm TestCafe/Node/browser, native automation mode, CI, and reporter versions. Produce fixtures/tests/config compatible with the existing runner; missing config is open, not an implicit upgrade.
- Initialize isolated sessions with Roles or independent identities and isolate accounts/business keys too. Await asynchronous t actions and use supported Selector/assertion waits rather than fixed sleeps.
- Verify paid state, amount, and principal. Boundary stubs must not bypass the real UI; a normal title is no success. Negative controls must fail business assertions.
- CLI nonzero or programmatic failedCount>0 must fail CI. Reporters cannot swallow failures; retain screenshots/console/test IDs and cleanup. Parseable config is distinct from actual execution.
Common Pitfalls
- Do not use it with vague scope and no context.
- Do not treat every area as equally important.
- Do not skip assumptions and missing information.
Best Practices
-
Start from the prompt file, then add only the context that matters.
-
Keep the output risk-driven and executable.
-
If the request is incomplete, return a usable first version and mark gaps.
-
To verify generated business assertions, failure propagation or isolation, read evals/fixtures/checkout-app/README.md and its local good/bug/timeout controls; execute only when a run is requested.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/naodeng/awesome-qa-skills/ui-test-testcafe">View ui-test-testcafe on skillZs</a>