Run any Skill in Manus with one click

open-testing-convert-codeceptjs

Stars13

Forks1

UpdatedApril 20, 2026 at 11:58

Convert CodeceptJS test suites (`I.amOnPage`, `I.fillField`, `I.click`, `I.see`, `I.grabTextFrom`, `Feature('...')`, `Scenario('...', ({I}) => ...)`, Page Objects, helpers Playwright/Puppeteer/WebDriver) to and from Selenium, Playwright, Cypress, WebDriverIO, Puppeteer, Appium, Cucumber, Eggplant (SenseTalk), TestCafe, Nightwatch, OpenTest.AI, Testers.AI Recorder, and Testers.AI Dynamic. Handles CodeceptJS's actor-based API, multi-helper backend, semantic locator shortcuts, data-driven `Data([...]).Scenario`, and BDD mode. Use whenever the user wants to migrate a CodeceptJS suite, port CodeceptJS tests to Playwright/Cypress, or round-trip CodeceptJS through OpenTest.AI. MANDATORY TRIGGERS — "convert CodeceptJS", "CodeceptJS to <target>", "migrate CodeceptJS", "port CodeceptJS", "codecept.conf", any mention of CodeceptJS alongside any supported target.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

AgenticTesting

AgenticTesting/OpenTestingAI

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

File Explorer

4 files

SKILL.md

readonly

name	open-testing-convert-codeceptjs
description	Convert CodeceptJS test suites (`I.amOnPage`, `I.fillField`, `I.click`, `I.see`, `I.grabTextFrom`, `Feature('...')`, `Scenario('...', ({I}) => ...)`, Page Objects, helpers Playwright/Puppeteer/WebDriver) to and from Selenium, Playwright, Cypress, WebDriverIO, Puppeteer, Appium, Cucumber, Eggplant (SenseTalk), TestCafe, Nightwatch, OpenTest.AI, Testers.AI Recorder, and Testers.AI Dynamic. Handles CodeceptJS's actor-based API, multi-helper backend, semantic locator shortcuts, data-driven `Data([...]).Scenario`, and BDD mode. Use whenever the user wants to migrate a CodeceptJS suite, port CodeceptJS tests to Playwright/Cypress, or round-trip CodeceptJS through OpenTest.AI. MANDATORY TRIGGERS — "convert CodeceptJS", "CodeceptJS to <target>", "migrate CodeceptJS", "port CodeceptJS", "codecept.conf", any mention of CodeceptJS alongside any supported target.
license	MIT
metadata	{"family":"open-testing-convert","source":"codeceptjs","orchestrator":"open-testing-convert","targets":["selenium","playwright","cypress","webdriverio","puppeteer","appium","cucumber","eggplant","testcafe","nightwatch","opentestai","testersai-recorder","testersai-dynamic"]}

Convert — CodeceptJS

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

When to use

Trigger when:

Imports: const { I } = inject() or direct Feature('...') / Scenario('...', ({I}) => ...).
codecept.conf.js / codecept.conf.ts config file.
Actor-based API: I.amOnPage, I.fillField, I.click, I.see, I.dontSee, I.grabTextFrom, etc.
Helpers declared in config: Playwright, Puppeteer, WebDriver, Appium, REST.
Scenario syntax: Scenario('Valid login', ({I}) => {...}).
codeceptjs / @codeceptjs/ui dependency in package.json.

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

CodeceptJS 3.x (modern) and 2.x (legacy) codebases.
Helpers: Playwright, Puppeteer, WebDriver (Selenium), Appium, Nightmare, TestCafe, REST, GraphQL, MockServer.
Page Objects (actor-like classes with methods) and Page Fragments.
Data-driven: Data([...]).Scenario('name', ({I, current}) => ...).
BDD mode: .feature + step_definitions.
Scenario hooks: Before/After/BeforeSuite/AfterSuite.
Parallel execution, retries, tags, dataTable.
Semantic locators: 'Sign in' resolves to button/link by text.
Custom helpers (user-defined Helper classes).

Out of scope

CodeceptUI (GUI) artifacts — not test content.
Cloud services integration (SauceLabs/BrowserStack) — preserved as config metadata only.
Legacy class: syntax with DataTable XML — convert to Data([]) first.

Quick reference

CodeceptJS	Canonical	Example target
`I.amOnPage(u)`	`{kind: "navigate", url: u}`	Playwright `page.goto`
`I.click('Sign in')`	`{kind: "click", locator: {strategy: "semantic_text", value: "Sign in"}}`	framework-specific
`I.fillField('#x', 'v')`	`{kind: "input", locator, value}`	framework-specific
`I.see('Welcome')`	`{kind: "assert", assertion_kind: "text_visible", value: "Welcome"}`	framework-specific
`I.seeElement('#x')`	`{kind: "assert", assertion_kind: "element_visible", locator}`	framework-specific
`I.grabTextFrom('#x')`	`{kind: "js_exec", semantic: "grab_text", locator, result_var}`	framework-specific
`await loginPage.login(u, p)`	expanded page object method → inline steps	framework-specific

See reference/mappings.md for full cookbook.

More from this repository

same 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-codeceptjs
description	Convert CodeceptJS test suites (`I.amOnPage`, `I.fillField`, `I.click`, `I.see`, `I.grabTextFrom`, `Feature('...')`, `Scenario('...', ({I}) => ...)`, Page Objects, helpers Playwright/Puppeteer/WebDriver) to and from Selenium, Playwright, Cypress, WebDriverIO, Puppeteer, Appium, Cucumber, Eggplant (SenseTalk), TestCafe, Nightwatch, OpenTest.AI, Testers.AI Recorder, and Testers.AI Dynamic. Handles CodeceptJS's actor-based API, multi-helper backend, semantic locator shortcuts, data-driven `Data([...]).Scenario`, and BDD mode. Use whenever the user wants to migrate a CodeceptJS suite, port CodeceptJS tests to Playwright/Cypress, or round-trip CodeceptJS through OpenTest.AI. MANDATORY TRIGGERS — "convert CodeceptJS", "CodeceptJS to <target>", "migrate CodeceptJS", "port CodeceptJS", "codecept.conf", any mention of CodeceptJS alongside any supported target.
license	MIT
metadata	{"family":"open-testing-convert","source":"codeceptjs","orchestrator":"open-testing-convert","targets":["selenium","playwright","cypress","webdriverio","puppeteer","appium","cucumber","eggplant","testcafe","nightwatch","opentestai","testersai-recorder","testersai-dynamic"]}

Convert — CodeceptJS

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

When to use

Trigger when:

Imports: const { I } = inject() or direct Feature('...') / Scenario('...', ({I}) => ...).
codecept.conf.js / codecept.conf.ts config file.
Actor-based API: I.amOnPage, I.fillField, I.click, I.see, I.dontSee, I.grabTextFrom, etc.
Helpers declared in config: Playwright, Puppeteer, WebDriver, Appium, REST.
Scenario syntax: Scenario('Valid login', ({I}) => {...}).
codeceptjs / @codeceptjs/ui dependency in package.json.

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

CodeceptJS 3.x (modern) and 2.x (legacy) codebases.
Helpers: Playwright, Puppeteer, WebDriver (Selenium), Appium, Nightmare, TestCafe, REST, GraphQL, MockServer.
Page Objects (actor-like classes with methods) and Page Fragments.
Data-driven: Data([...]).Scenario('name', ({I, current}) => ...).
BDD mode: .feature + step_definitions.
Scenario hooks: Before/After/BeforeSuite/AfterSuite.
Parallel execution, retries, tags, dataTable.
Semantic locators: 'Sign in' resolves to button/link by text.
Custom helpers (user-defined Helper classes).

Out of scope

CodeceptUI (GUI) artifacts — not test content.
Cloud services integration (SauceLabs/BrowserStack) — preserved as config metadata only.
Legacy class: syntax with DataTable XML — convert to Data([]) first.

Quick reference

CodeceptJS	Canonical	Example target
`I.amOnPage(u)`	`{kind: "navigate", url: u}`	Playwright `page.goto`
`I.click('Sign in')`	`{kind: "click", locator: {strategy: "semantic_text", value: "Sign in"}}`	framework-specific
`I.fillField('#x', 'v')`	`{kind: "input", locator, value}`	framework-specific
`I.see('Welcome')`	`{kind: "assert", assertion_kind: "text_visible", value: "Welcome"}`	framework-specific
`I.seeElement('#x')`	`{kind: "assert", assertion_kind: "element_visible", locator}`	framework-specific
`I.grabTextFrom('#x')`	`{kind: "js_exec", semantic: "grab_text", locator, result_var}`	framework-specific
`await loginPage.login(u, p)`	expanded page object method → inline steps	framework-specific

See reference/mappings.md for full cookbook.