mcpField
U
ui-test-testcafe

ui-test-testcafe

github.com/naodengTesting & quality28540 installsUpdated today
Repository

About ui-test-testcafe

A skill for planning and producing TestCafe UI tests, for projects using TestCafe or seeking TestCafe-ready work. It emphasizes compatibility with the existing runner, isolated test sessions, and business-level assertions.

Key features

  1. 01TestCafe-focused test planning
  2. 02Runner compatibility checks
  3. 03Isolated sessions and fixtures
  4. 04Business-state assertions
  5. 05CI failure propagation

Use cases

  1. 01Planning UI tests for an existing TestCafe project
  2. 02Isolating test accounts and sessions
  3. 03Ensuring failed tests fail CI

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/naodeng/awesome-qa-skills --skill ui-test-testcafe

After installing, type/ui-test-testcafein Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

README.md
agents/
openai.yaml
evals/
eval.yaml
evals/cases/
basic-success.yaml
domain-method-regression.yaml
edge-incomplete-input.yaml
edge-scope-boundary.yaml
evals/fixtures/
check_domain_decisions.py
check-domain-decisions.sh
domain-oracle.json
evals/fixtures/checkout-app/
checkout.test.js
index.html
README.md
receipt.html
server.mjs
examples/
sample-context.md
output-templates/
template-markdown.md
prompts/
ui-test-testcafe.md
references/
domain-decision-example.md
framework-spec.md
setup-and-ci.md
scripts/
run-tests.sh

Details

From the project README

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

  1. Open prompts/ui-test-testcafe.md and use it as the main prompt.
  2. Add the real project context: scope, environment, constraints, risks, dependencies, and expected deliverable.
  3. 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

  1. 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.
  2. 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.
  3. 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.
  4. 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.

Comments

Markdown supported