← ClaudeAtlas

test-case-to-katalon-studiolisted

Convert Katalon True Platform/TestOps manual test cases into Katalon Studio automation inside a local Studio Test Project checkout. Use when you need to author or extend a .tc test case file and its paired Groovy script under Scripts/, keep test case variable GUIDs consistent with the .ts test suite bindings that read them, model page elements as .rs test objects in the Object Repository instead of inline selectors, write WebUI, Mobile, or WS keyword steps in Groovy with Java interop, or wire data files, execution profiles, and GlobalVariable into a generated case. Also use to decide whether a headless katalonc run is possible at all, since Katalon Runtime Engine is a separately licensed paid runtime whose CLI requires -apiKey. Once a Studio run has finished and its report exists, hand off to upload-report. Written for the automation tester who has to land a manual case inside a Katalon Studio project rather than a code-first framework.
katalon-labs/true-skills · ★ 7 · AI & Automation · score 78
Install: claude install-skill katalon-labs/true-skills
# Katalon Test Case To Katalon Studio Use this skill to turn Katalon Platform/TestOps manual test cases into Katalon Studio automation: `.tc` metadata, the paired Groovy script, Object Repository test objects, and the test suite that binds data to them. Prefer the conventions the target project already uses. Treat the human as a tool: ask concise questions whenever a project path, credential, selector, or test data value cannot be discovered safely. ## Availability Boundary State the boundary before promising automation. It has three parts and none of them is optional. **Available through Katalon MCP** - Resolve context with `list_projects` and `list_repositories`. - Read the source case with `find_test_cases` and `read_test_case`; resolve a requirement key with `find_requirements`, `read_requirement`, and `find_test_cases_by_requirement`. - Read platform-side suites with `find_test_suites` and `read_test_suite`. - Write the generated Studio path back onto the platform case with `update_test_case`, for traceability. **Not available through Katalon MCP** - No MCP tool reads or writes a Studio project file. `.prj`, `.tc`, `.rs`, `.ts`, `.glbl`, `.dat`, and everything under `Scripts/` live on disk only. Work on a local checkout and ask the human for the path. - No MCP tool captures web objects. Web Spy and Record are Studio desktop features; write `.rs` files by hand. - No MCP tool inspects the live application. Use Browser/Playwright to discover selectors, then encode th