Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

open-testing-convert-testcafe

Sterne13

Forks1

Aktualisiert20. April 2026 um 11:58

Convert TestCafe test suites (`fixture('...')`, `test('...')`, `Selector('...')`, `t.click`, `t.typeText`, `t.expect(...).ok/eql/contains`, `ClientFunction`, `Role`) to and from Selenium, Playwright, Cypress, WebDriverIO, Puppeteer, Appium, Cucumber, Eggplant (SenseTalk), OpenTest.AI, Testers.AI Recorder, and Testers.AI Dynamic. Handles TestCafe's proxy-based driver, smart auto-waits, roles-based auth, client-side JS execution, and iframe/native-dialog support. Use whenever the user wants to migrate a TestCafe suite, port TestCafe tests to Playwright/Cypress, or round-trip TestCafe through OpenTest.AI. MANDATORY TRIGGERS — "convert TestCafe", "TestCafe to <target>", "migrate TestCafe", "port TestCafe", ".testcaferc", any mention of TestCafe alongside any supported target.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

AgenticTesting

AgenticTesting/OpenTestingAI

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Softwarequalitätssicherungsanalysten und -testerInformatik- und Mathematikberufe·SOC 15-1253

Datei-Explorer

4 Dateien

SKILL.md

readonly

name	open-testing-convert-testcafe
description	Convert TestCafe test suites (`fixture('...')`, `test('...')`, `Selector('...')`, `t.click`, `t.typeText`, `t.expect(...).ok/eql/contains`, `ClientFunction`, `Role`) to and from Selenium, Playwright, Cypress, WebDriverIO, Puppeteer, Appium, Cucumber, Eggplant (SenseTalk), OpenTest.AI, Testers.AI Recorder, and Testers.AI Dynamic. Handles TestCafe's proxy-based driver, smart auto-waits, roles-based auth, client-side JS execution, and iframe/native-dialog support. Use whenever the user wants to migrate a TestCafe suite, port TestCafe tests to Playwright/Cypress, or round-trip TestCafe through OpenTest.AI. MANDATORY TRIGGERS — "convert TestCafe", "TestCafe to <target>", "migrate TestCafe", "port TestCafe", ".testcaferc", any mention of TestCafe alongside any supported target.
license	MIT
metadata	{"family":"open-testing-convert","source":"testcafe","orchestrator":"open-testing-convert","targets":["selenium","playwright","cypress","webdriverio","puppeteer","appium","cucumber","eggplant","opentestai","testersai-recorder","testersai-dynamic"]}

Convert — TestCafe

Converts TestCafe test suites to any supported target, and emits TestCafe from any source.

When to use

Trigger when:

Imports: import { Selector, ClientFunction, Role, t } from 'testcafe'.
Top-level fixture('...') + test('...', async t => ...).
.testcaferc.json / .testcaferc.js config files.
Proxy-based driver (no WebDriver session) — TestCafe serves a proxy at http://localhost:1337.
Smart auto-wait patterns: chained .click().typeText().expect(...) without explicit waits.

How to use

Read the master orchestrator first.
Read this skill's reference files: source-profile.md, extraction.md, mappings.md.
Read target primer for your target.
Emit per target Emission Checklist.

Scope

TestCafe 1.x and 2.x.
Mocha/Jasmine-less (TestCafe has its own runner).
Role for authentication reuse.
ClientFunction / RequestHook / RequestLogger / RequestMock.
Custom assertion methods via t.expect(...).method(...).
Concurrency (-c N) — noted in preamble; doesn't affect canonical.
Browser targets: Chrome, Firefox, Safari, Edge, mobile emulation.

Out of scope

TestCafe Studio visual-editor artifacts — those export to standard TestCafe JS, so converge to this skill.
TestCafe plugins (testcafe-reporter-*) — preserved as config metadata, not converted.

Quick reference

TestCafe	Canonical	Example target
`await t.navigateTo(url)`	`{kind: "navigate", url}`	Playwright `page.goto`
`await t.click(Selector('#x'))`	`{kind: "click", locator}`	framework-specific
`await t.typeText(Selector('#x'), 'v')`	`{kind: "input", locator, value}`	framework-specific
`await t.expect(Selector('#x').innerText).eql('Welcome')`	`{kind: "assert", assertion_kind: "text_equals"}`	framework-specific
`await t.useRole(adminRole)`	`{kind: "session_use", role_name: "admin"}`	Playwright `storageState`; Cypress `cy.session`
`await ClientFunction(() => window.location.href)()`	`{kind: "js_exec", code, result_var}`	framework-specific

See reference/mappings.md for full cookbook.

Mehr aus diesem Repository

gleiches Repository

open-testing-coverage

AgenticTesting/OpenTestingAI

Test coverage analysis, gap detection, coverage reporting, and coverage optimization using the COVERED agent pipeline. Use this skill whenever the user mentions test coverage, coverage analysis, coverage gaps, traceability matrix, coverage heat map, coverage dashboard, coverage metrics, coverage trends, test intensity, risk-based coverage, requirement coverage, code coverage mapping, or wants to know if their testing is sufficient. Also trigger when users ask about uncovered requirements, orphaned tests, coverage regression, or coverage targets. MANDATORY TRIGGERS: coverage, traceability, gap analysis, RTM, heat map, coverage dashboard, coverage trend, test intensity evaluation.

2026-05-1413

open-testing-create

AgenticTesting/OpenTestingAI

Generate concrete test cases, test data, and test scripts from a test design technique and context. Applies 106 test design techniques (boundary value analysis, equivalence partitioning, decision tables, state transitions, pairwise, combinatorial, etc.) to enumerate test conditions and author realistic test cases with inputs, expected results, and traceability. Use this skill whenever the user needs to: create test cases from a technique, apply a testing method to requirements, generate test data, design test scenarios, or populate test scripts. Triggers include: 'test cases', 'create tests', 'test design', 'apply [technique name]', 'generate test data', 'test scenarios', or any technique name (BVA, EP, combinatorial, etc.).technique name (BVA, EP, combinatorial, etc.).

2026-05-1413

open-testing-design

AgenticTesting/OpenTestingAI

Generate comprehensive test strategies, quality engineering approaches, risk analysis, and optimal technique selection. Use this when you need to develop test strategies, perform quality risk analysis, select test design techniques, assess testability, estimate test effort, define governance structures, or establish test exit criteria and coverage targets.

2026-05-1413

open-testing-management

AgenticTesting/OpenTestingAI

Test management, defect management, process evaluation, and maturity assessment using the MANAGES agent pipeline. Use this skill whenever the user mentions test management, defect management, process improvement, TMMi, maturity assessment, ARCI matrix, quality policy, test policy, process evaluation, defect lifecycle, triage, test process, roles and responsibilities, QAM, QPM, GTA, generic test agreements, process maturity, test improvement, or wants to evaluate and improve their testing practices. Also trigger for defect tracking, anomaly management, process compliance, test governance, or organizational testing capability. MANDATORY TRIGGERS: test management, defect management, TMMi, maturity, ARCI, process improvement, quality policy, defect lifecycle, process evaluation, test governance.

2026-05-1413

open-testing-plan

AgenticTesting/OpenTestingAI

Generate comprehensive test plans, schedules, resource allocation, environment setup, and test data strategies. Use this when you need to develop master test plans, level-specific test plans, allocate resources and environments, plan non-functional testing, define end-to-end testing chains, or establish test data management strategies.

2026-05-1413

open-testing-reporting

AgenticTesting/OpenTestingAI

Test reporting, progress dashboards, release advice, and final test reports using the REPORTS agent pipeline. Use this skill whenever the user mentions test report, progress report, test dashboard, release advice, go/no-go decision, test metrics, defect trends, test execution summary, quality assessment, final test report, lessons learned, RAG status, or wants to generate any kind of testing status or quality report. Also trigger for executive summaries, sprint test reports, release readiness, or stakeholder communication about testing. MANDATORY TRIGGERS: test report, progress, dashboard, release advice, go/no-go, test metrics, defect trend, RAG status, quality report, test summary

2026-05-1413

name	open-testing-convert-testcafe
description	Convert TestCafe test suites (`fixture('...')`, `test('...')`, `Selector('...')`, `t.click`, `t.typeText`, `t.expect(...).ok/eql/contains`, `ClientFunction`, `Role`) to and from Selenium, Playwright, Cypress, WebDriverIO, Puppeteer, Appium, Cucumber, Eggplant (SenseTalk), OpenTest.AI, Testers.AI Recorder, and Testers.AI Dynamic. Handles TestCafe's proxy-based driver, smart auto-waits, roles-based auth, client-side JS execution, and iframe/native-dialog support. Use whenever the user wants to migrate a TestCafe suite, port TestCafe tests to Playwright/Cypress, or round-trip TestCafe through OpenTest.AI. MANDATORY TRIGGERS — "convert TestCafe", "TestCafe to <target>", "migrate TestCafe", "port TestCafe", ".testcaferc", any mention of TestCafe alongside any supported target.
license	MIT
metadata	{"family":"open-testing-convert","source":"testcafe","orchestrator":"open-testing-convert","targets":["selenium","playwright","cypress","webdriverio","puppeteer","appium","cucumber","eggplant","opentestai","testersai-recorder","testersai-dynamic"]}

Convert — TestCafe

Converts TestCafe test suites to any supported target, and emits TestCafe from any source.

When to use

Trigger when:

Imports: import { Selector, ClientFunction, Role, t } from 'testcafe'.
Top-level fixture('...') + test('...', async t => ...).
.testcaferc.json / .testcaferc.js config files.
Proxy-based driver (no WebDriver session) — TestCafe serves a proxy at http://localhost:1337.
Smart auto-wait patterns: chained .click().typeText().expect(...) without explicit waits.

How to use

Read the master orchestrator first.
Read this skill's reference files: source-profile.md, extraction.md, mappings.md.
Read target primer for your target.
Emit per target Emission Checklist.

Scope

TestCafe 1.x and 2.x.
Mocha/Jasmine-less (TestCafe has its own runner).
Role for authentication reuse.
ClientFunction / RequestHook / RequestLogger / RequestMock.
Custom assertion methods via t.expect(...).method(...).
Concurrency (-c N) — noted in preamble; doesn't affect canonical.
Browser targets: Chrome, Firefox, Safari, Edge, mobile emulation.

Out of scope

TestCafe Studio visual-editor artifacts — those export to standard TestCafe JS, so converge to this skill.
TestCafe plugins (testcafe-reporter-*) — preserved as config metadata, not converted.

Quick reference

TestCafe	Canonical	Example target
`await t.navigateTo(url)`	`{kind: "navigate", url}`	Playwright `page.goto`
`await t.click(Selector('#x'))`	`{kind: "click", locator}`	framework-specific
`await t.typeText(Selector('#x'), 'v')`	`{kind: "input", locator, value}`	framework-specific
`await t.expect(Selector('#x').innerText).eql('Welcome')`	`{kind: "assert", assertion_kind: "text_equals"}`	framework-specific
`await t.useRole(adminRole)`	`{kind: "session_use", role_name: "admin"}`	Playwright `storageState`; Cypress `cy.session`
`await ClientFunction(() => window.location.href)()`	`{kind: "js_exec", code, result_var}`	framework-specific

See reference/mappings.md for full cookbook.