Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

open-testing-convert-puppeteer

Étoiles13

Forks1

Mis à jour20 avril 2026 à 11:58

Convert Puppeteer test suites (`puppeteer.launch`, `page.goto`, `page.click`, `page.type`, `page.$`/`page.$$`, `page.waitForSelector`, `page.evaluate`, typically paired with Jest/Mocha) to and from Selenium, Playwright, Cypress, Appium, Cucumber, Eggplant (SenseTalk), OpenTest.AI, Testers.AI Recorder, and Testers.AI Dynamic. Handles Puppeteer-core and full Puppeteer, headless/headed modes, ARIA selectors, XPath, network interception via `page.setRequestInterception`, and iframe/worker handling. Use whenever the user wants to migrate a Puppeteer suite, port Puppeteer tests to Playwright/Selenium/Cypress, or round-trip through OpenTest.AI. MANDATORY TRIGGERS — "convert Puppeteer", "Puppeteer to <target>", "Puppeteer to Playwright", "migrate Puppeteer", "port Puppeteer", "puppeteer-core to Playwright", any mention of Puppeteer alongside any supported target.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

AgenticTesting

AgenticTesting/OpenTestingAI

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en assurance qualité des logiciels et testeursProfessions informatiques et mathématiques·SOC 15-1253

Explorateur de fichiers

4 fichiers

SKILL.md

readonly

name	open-testing-convert-puppeteer
description	Convert Puppeteer test suites (`puppeteer.launch`, `page.goto`, `page.click`, `page.type`, `page.$`/`page.$$`, `page.waitForSelector`, `page.evaluate`, typically paired with Jest/Mocha) to and from Selenium, Playwright, Cypress, Appium, Cucumber, Eggplant (SenseTalk), OpenTest.AI, Testers.AI Recorder, and Testers.AI Dynamic. Handles Puppeteer-core and full Puppeteer, headless/headed modes, ARIA selectors, XPath, network interception via `page.setRequestInterception`, and iframe/worker handling. Use whenever the user wants to migrate a Puppeteer suite, port Puppeteer tests to Playwright/Selenium/Cypress, or round-trip through OpenTest.AI. MANDATORY TRIGGERS — "convert Puppeteer", "Puppeteer to <target>", "Puppeteer to Playwright", "migrate Puppeteer", "port Puppeteer", "puppeteer-core to Playwright", any mention of Puppeteer alongside any supported target.
license	MIT
metadata	{"family":"open-testing-convert","source":"puppeteer","orchestrator":"open-testing-convert","targets":["selenium","playwright","cypress","appium","cucumber","eggplant","opentestai","testersai-recorder","testersai-dynamic"]}

Convert — Puppeteer

Converts Puppeteer test suites to any supported target. Defers orchestration to open-testing-convert.

When to use

Trigger when:

Imports like import puppeteer from 'puppeteer' or const puppeteer = require('puppeteer-core').
Calls puppeteer.launch(...), browser.newPage(), page.goto(...), page.click(...), page.type(...), page.$(...), page.$$(...), page.waitForSelector(...), page.evaluate(...), page.screenshot(...).
Paired with a test runner (Jest, Mocha, Jasmine, or bare Node runner).
jest-puppeteer preset (jest-puppeteer.config.js, global-teardown.js).

How to use

Read the master orchestrator first.
Detect runner (Jest/Mocha/bare). Runner-specific lifecycle extraction differs.
Determine puppeteer vs puppeteer-core — core is thinner, launches externally. Canonical behaviour is identical.
Read target primer for your target.
Read this skill's reference files: source-profile.md, extraction.md, mappings.md.
Emit per target Emission Checklist.

Scope

Puppeteer 20+ (with ARIA selectors).
Puppeteer legacy (pre-20, CSS-only by default).
puppeteer-core (headless-shell or external Chromium path).
Jest + jest-puppeteer preset.
Mocha/Jasmine standalone with beforeAll/afterAll browser lifecycle.
Bare Node scripts using Puppeteer for crawling/scraping (converted to tests with synthesized describe/it).

Out of scope

Puppeteer Sharp (C#) — separate skill trigger (not in the catalogue).
Headless Chrome via raw CDP (Chrome DevTools Protocol) — route separately.

Canonical-intent coverage notes

Puppeteer → Playwright is the smoothest translation in this catalogue (shared mental model, overlapping API). Other targets incur the usual mapping cost.

Quick reference

Puppeteer	Canonical	Target example
`page.goto(url)`	`{kind: "navigate", url}`	Playwright `page.goto`; Cypress `cy.visit`
`page.click(sel)`	`{kind: "click", locator}`	framework-specific
`page.type(sel, v)`	`{kind: "input", locator, value: v}`	framework-specific
`page.$eval(sel, fn)`	`{kind: "js_exec", locator, code}`	preserve if target supports
`page.waitForSelector(sel)`	`{kind: "wait_for", wait_kind: "element_visible"}`	framework-specific
`page.waitForResponse(url)`	`{kind: "wait_for", wait_kind: "response", url}`	Playwright `waitForResponse`; Cypress `cy.wait('@alias')`
ARIA: `page.$('aria/Sign in[role="button"]')`	`{kind: "click", locator: {role: "button", name: "Sign in"}}`	Playwright `getByRole`
`page.screenshot({path})`	`{kind: "screenshot", name}`	framework-specific

See reference/mappings.md for the full cookbook.

Plus depuis ce dépôt

même dépôt

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-puppeteer
description	Convert Puppeteer test suites (`puppeteer.launch`, `page.goto`, `page.click`, `page.type`, `page.$`/`page.$$`, `page.waitForSelector`, `page.evaluate`, typically paired with Jest/Mocha) to and from Selenium, Playwright, Cypress, Appium, Cucumber, Eggplant (SenseTalk), OpenTest.AI, Testers.AI Recorder, and Testers.AI Dynamic. Handles Puppeteer-core and full Puppeteer, headless/headed modes, ARIA selectors, XPath, network interception via `page.setRequestInterception`, and iframe/worker handling. Use whenever the user wants to migrate a Puppeteer suite, port Puppeteer tests to Playwright/Selenium/Cypress, or round-trip through OpenTest.AI. MANDATORY TRIGGERS — "convert Puppeteer", "Puppeteer to <target>", "Puppeteer to Playwright", "migrate Puppeteer", "port Puppeteer", "puppeteer-core to Playwright", any mention of Puppeteer alongside any supported target.
license	MIT
metadata	{"family":"open-testing-convert","source":"puppeteer","orchestrator":"open-testing-convert","targets":["selenium","playwright","cypress","appium","cucumber","eggplant","opentestai","testersai-recorder","testersai-dynamic"]}

Convert — Puppeteer

Converts Puppeteer test suites to any supported target. Defers orchestration to open-testing-convert.

When to use

Trigger when:

Imports like import puppeteer from 'puppeteer' or const puppeteer = require('puppeteer-core').
Calls puppeteer.launch(...), browser.newPage(), page.goto(...), page.click(...), page.type(...), page.$(...), page.$$(...), page.waitForSelector(...), page.evaluate(...), page.screenshot(...).
Paired with a test runner (Jest, Mocha, Jasmine, or bare Node runner).
jest-puppeteer preset (jest-puppeteer.config.js, global-teardown.js).

How to use

Read the master orchestrator first.
Detect runner (Jest/Mocha/bare). Runner-specific lifecycle extraction differs.
Determine puppeteer vs puppeteer-core — core is thinner, launches externally. Canonical behaviour is identical.
Read target primer for your target.
Read this skill's reference files: source-profile.md, extraction.md, mappings.md.
Emit per target Emission Checklist.

Scope

Puppeteer 20+ (with ARIA selectors).
Puppeteer legacy (pre-20, CSS-only by default).
puppeteer-core (headless-shell or external Chromium path).
Jest + jest-puppeteer preset.
Mocha/Jasmine standalone with beforeAll/afterAll browser lifecycle.
Bare Node scripts using Puppeteer for crawling/scraping (converted to tests with synthesized describe/it).

Out of scope

Puppeteer Sharp (C#) — separate skill trigger (not in the catalogue).
Headless Chrome via raw CDP (Chrome DevTools Protocol) — route separately.

Canonical-intent coverage notes

Puppeteer → Playwright is the smoothest translation in this catalogue (shared mental model, overlapping API). Other targets incur the usual mapping cost.

Quick reference

Puppeteer	Canonical	Target example
`page.goto(url)`	`{kind: "navigate", url}`	Playwright `page.goto`; Cypress `cy.visit`
`page.click(sel)`	`{kind: "click", locator}`	framework-specific
`page.type(sel, v)`	`{kind: "input", locator, value: v}`	framework-specific
`page.$eval(sel, fn)`	`{kind: "js_exec", locator, code}`	preserve if target supports
`page.waitForSelector(sel)`	`{kind: "wait_for", wait_kind: "element_visible"}`	framework-specific
`page.waitForResponse(url)`	`{kind: "wait_for", wait_kind: "response", url}`	Playwright `waitForResponse`; Cypress `cy.wait('@alias')`
ARIA: `page.$('aria/Sign in[role="button"]')`	`{kind: "click", locator: {role: "button", name: "Sign in"}}`	Playwright `getByRole`
`page.screenshot({path})`	`{kind: "screenshot", name}`	framework-specific

See reference/mappings.md for the full cookbook.