open-testing-convert

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.

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.

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.

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.

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.

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.