test-maintenancelisted

Maintain and evolve a Katalon True Platform/TestOps regression suite as the application changes. Use when you need to detect which tests broke or became flaky from stability and result history, diagnose whether a case needs repair vs regeneration, repair test assets (update, move, reorganize cases), refresh coverage after application or requirement changes, and feed the resulting gap list back into planning. Closes the lifecycle loop. For classifying a specific run's failures use analyze-failures; for authoring brand-new cases use create-test-cases.
katalon-labs/true-skills · ★ 3 · AI & Automation · score 67

Install: claude install-skill katalon-labs/true-skills

# Katalon Test Maintenance Use this skill for the **maintenance** stage: keep the regression suite healthy over time and feed learning back to the plan. It consumes failure/stability signals and produces repairs plus a refreshed coverage gap list. ## Availability Boundary - **Available via MCP:** change/impact signals (`fetch_test_stability_data`, `find_test_results`, `read_execution`), and case-level repair (`update_test_case`, `move_test_case`, `duplicate_test_case`). - **Not directly available:** Self-healing tests, Time Capsule, Studio Tracer, object refactoring, and StudioAssist Agent-mode edits are **Studio-desktop** features. TrueTest regeneration from live journeys is a **TrueTest** surface. Narrate these; MCP repairs are case-level content edits, not object/script self-healing. ## Maintenance Workflow ```text +---------------------+ +----------------------+ +----------------------+ | Detect change impact| --> | Diagnose: repair vs | --> | Repair case assets | | stability + history | | regenerate vs retire | | update/move/dup | +---------------------+ +----------------------+ +----------------------+ | v +----------------------+ | Validate + feed back |