open-testing-convert-robot-framework

This skill converts Robot Framework test suites into multi-target formats like Browser, Cypress, and Appium. It translates .robot and .resource files while mapping keywords, variables, and setup/teardown into canonical representations suitable for your chosen downstream framework.

Yes, you can migrate Robot Framework keywords and variables to SeleniumLibrary and Appium. The conversion process preserves imports, variables, and keyword usage, applying structured mappings to generate target-specific test artifacts for diverse frameworks across local and CI environments.

You need a project with Robot Framework files (.robot, .resource) and references to libraries, resources, and variables. The converter processes these inputs to output canonical mappings and per-target emission configurations for your selected frameworks.

The best way to handle setup and teardown during Robot Framework migration is through canonical mapping. This skill translates setup and teardown structures into target-specific representations, preserving test logic while adapting them for frameworks like Cypress, Playwright, and SeleniumLibrary.

Yes, converting Robot Framework tests to Cypress preserves resource imports. The conversion process translates .resource files and library references into canonical representations, ensuring imports, variables, and keyword usage are maintained across multi-target outputs like Cypress and Appium.

You should use multi-target conversion when migrating legacy Robot Framework suites to modern CI pipelines or executing multi-target test strategies. It enables simultaneous translation to frameworks like SeleniumLibrary, Browser, Cypress, and Appium while preserving variables and keyword usage.