open-testing-convert

Name: open-testing-convert
Availability: InStock
Author: agentictesting

Route test-conversion requests to the appropriate per-source convert skill.

13|1|Updated Mar 16, 2026

Search Tags:#workflow #routing #orchestration #conversion #test-automation #framework-migration #per-source-skill

Ready to run

npx skills add https://github.com/AgenticTesting/OpenTestingAI --skill open-testing-convert

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: open-testing-convert
Source: https://github.com/AgenticTesting/OpenTestingAI/tree/main/.opentesting-convert/skills/open-testing-convert
Command: npx skills add https://github.com/AgenticTesting/OpenTestingAI --skill open-testing-convert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Master orchestrator for converting test automation scripts across 30 per-source convert skills, routing to the correct per-source or reverse-direction skill so translations are performed by the owner of the actual rules.

Core Features & Use Cases

Routes conversion requests by detecting the source framework, target framework, and optional languages.
Delegates to the appropriate per-source or reverse-direction skill that owns the actual translation rules.
Validates coverage against canonical IR, target primers, and deprecation notes, surfacing round-trips and fallback paths as needed.
Handles mid-matrix pairs by consulting both the source skill's mappings and the target skill's reverse-emission sections to resolve ambiguities.

Quick Start

Specify the source and target frameworks (and optional languages) to have the orchestrator route the request to the correct per-source convert skill.

Frequently Asked Questions about open-testing-convert

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I convert test automation scripts from one framework to another?▼

To convert test automation scripts, you specify the source framework, target framework, and optional languages so the orchestrator can route the request to the correct per-source skill that owns the translation rules.

What is cross-framework test conversion and how does the routing work?▼

Cross-framework test conversion translates test scripts between different automation frameworks. The master orchestrator detects the source and target frameworks, consulting a sources registry and target primers to delegate to the specific skill that owns the translation rules.

Can I convert test scripts for language-specific frameworks?▼

Yes, you can specify optional languages alongside the source and target frameworks. The orchestrator uses these parameters to validate coverage and route the request to the appropriate per-source skill.

How does the orchestrator handle deprecated frameworks or mid-matrix conversion pairs?▼

The orchestrator handles deprecations and mid-matrix pairs by consulting the source skill's mappings and the target skill's reverse-emission sections, resolving ambiguities through canonical IR and surfacing fallback paths as needed.

Do I need to manage the canonical IR or translation rules myself?▼

No, the master orchestrator does not emit translated code directly. It automatically consults the master sources registry, target primers, and canonical IR to select and delegate to the appropriate per-source skill that owns the translation rules.

What are the limitations of using an orchestrator for test framework migration?▼

The main limitation is coverage dependency; the orchestrator validates against a sources registry and deprecation notes. If a specific framework pairing lacks a dedicated per-source skill, it must surface fallback paths or round-trips through canonical IR instead of direct translation.