Migrate
Mabl
Move Mabl tests, flows, and plans to Autonomy. Replace recorded element models and auto-heal with intent-level steps.
Mabl tests are recorded, stored in Mabl's cloud, and exported as JSON or as generated Playwright. Export first, then migrate the export. Mabl flows become Autonomy Test Cases; Mabl plans become Test Plans.
Prompt
Paste this into a coding agent connected to the Autonomy MCP server from inside the repository:
Migrate the Mabl tests in this repository to Autonomy.
For each test: read it, then create one Autonomy Test Case with autonomy_test_case_create named after the test title.
Convert selectors into plain-language descriptions of the control. Keep every asserted value exactly as written.
Replace hard-coded credentials with agent-chosen fill values and configuration with environment values.
If the export is Mabl-generated Playwright, follow the Playwright mapping. Create one Autonomy Test Plan per Mabl plan and add the migrated cases as members with autonomy_test_plan_create. Drop waits, retries, and framework fixtures. List existing Test Cases first and skip any that already cover the journey.
Report a table of source test -> created Test Case ID when done.Mapping notes
- Element models and auto-heal are replaced by described targets; there is nothing to heal when the step names the control's intent.
- Mabl variables and data-driven tables become Environment values, or one Test Case per row when the rows differ in outcome.
- Mabl plan schedules and triggers become Autonomy Test Plans wired to GitHub or deployment webhooks.
- Mabl visual-change detection becomes Visual Compare with a linked reference.
See the migration overview for the full construct-by-construct mapping.