---
title: "How to move tests out of testRigor, mabl or Katalon into your repo"
description: "Check testRigor, mabl and Katalon export options, preserve test coverage and migrate bounded flows into Playwright, Cypress or Momentic."
canonical: "https://momentic.ai/blog/migrate-testrigor-mabl-katalon-tests-to-repo"
last-updated: "2026-11-10T17:36:30Z"
---

# How to move tests out of testRigor, mabl or Katalon into your repo

URL: https://momentic.ai/blog/migrate-testrigor-mabl-katalon-tests-to-repo

[blog](/blog) [/ resources](/blog/category/resources)  / migrate-testrigor-mabl-katalon-tests-to-repo

Resources

Check testRigor, mabl and Katalon export options, preserve test coverage and migrate bounded flows into Playwright, Cypress or Momentic.

Wei-Wei Wu

CEO, Momentic

## TL;DR

Check the real export path before rewriting a hosted suite. testRigor documents `testrigor clone` for exporting test cases, reusable rules and settings. mabl documents browser-test export to Playwright TypeScript and Selenium IDE, with unsupported steps. Katalon Studio already supports Git and can export native test artifacts between Studio projects.

An export can preserve source without making every test runnable in a different framework. Inventory the dependencies, export one representative flow, and prove the replacement catches the same failure before retiring the old check. Moving files into Git and replacing the execution engine are separate decisions.

## Comparison table

| Source or destination | Documented file or export path | What you can retain | What needs review | Pricing |
| --- | --- | --- | --- | --- |
| testRigor | CLI suite clone | Test cases, reusable rules and settings | Files retain testRigor syntax and execution semantics | See vendor pricing |
| mabl | CLI export to Playwright, Selenium IDE and data formats | Supported user-generated browser tests | Unsupported step types, selectors and runtime dependencies | See vendor pricing |
| Katalon Studio | Git projects and native artifact ZIP export | Test cases, objects, profiles and custom keywords | ZIP sharing targets Studio; other runners need adaptation | See vendor pricing |
| Playwright Test | Test code in your repo | Explicit browser actions, fixtures and assertions | Translation of vendor-specific behavior and setup | Open source; infrastructure separate |
| Cypress | Test code in your repo | Browser tests and supporting project code | Translation of commands, sessions and custom behavior | Open source runner; see service pricing |
| Momentic | Repository YAML; import of Momentic dashboard web tests | Plain-English steps in version-controlled files | No documented direct importer for these three vendors | See vendor pricing |

## Start by defining what must survive

List the behaviors, not only the test names. For each important flow, record the app build, authentication, starting data, expected result and cleanup. Include shared rules, object repositories, variables, scripts and external services the test uses.

Preserve negative checks too. A migrated login test that only opens the sign-in form does not replace a test that proved invalid credentials were rejected. An exported test that skips a download assertion has less coverage even if its remaining steps pass.

Decide whether you want source control while keeping the current runner, or whether you need to leave that runner. The first goal can require much less work. Do not rewrite a working suite solely because someone assumed it had no file-based path.

## testRigor: clone the suite before planning a rewrite

testRigor's [suite-export release documentation](https://testrigor.com/releases/passkey-authentication-testing-and-test-suite-export-via-cli/) states that its CLI can export test cases, reusable rules and settings from a specific suite. With its CLI installed and configured, replace `SUITE_ID` with your suite's ID:

`testrigor clone SUITE_ID`

Its [command-line documentation](https://testrigor.com/command-line/) also describes loading cases from YAML or text files, rules from YAML and settings from YAML or JSON. File-based test management is therefore a real option, not a hypothetical request to the vendor.

**Keep it if** your main requirement is versioning those test inputs while continuing to use testRigor.

**Watch for** equating source export with an independent execution engine. A plain-English command still has testRigor's interpretation. Playwright, Cypress and Momentic do not execute it merely because the file is in Git. If you change runners, port each action and assertion deliberately, including reusable rules and suite settings.

**Pricing** See vendor pricing for the testRigor execution you retain. A CLI export does not establish a different licensing model.

## mabl: use the real code export, then audit omissions

mabl's [Exporting tests from the CLI](https://help.mabl.com/hc/en-us/articles/19084077703444-Exporting-tests-from-the-CLI) documents Playwright TypeScript and Selenium IDE exports for browser tests. It also offers native/data formats. The command reference lists YAML as the default format, with JSON, CSV, Playwright and SIDE as choices.

For example, its documented Playwright export accepts an environment ID to choose the learned element information used for selectors. Replace the placeholders with your IDs:

`mabl tests export TEST_ID --format playwright --environment-id ENVIRONMENT_ID`

**Use it if** you want a code-first browser suite and the export supports the important steps in your tests. It can give you a starting point instead of a blank file.

**Watch for** the limitations. The documentation excludes generated tests such as the link crawler and visual smoke tests. Unsupported code-export steps include JavaScript snippets, API steps, file uploads, download assertions and MFA authenticator steps. Selenium export also does not support conditional steps. Review the full current list against your suite before estimating migration effort.

Do not confuse this with exporting run artifacts. Screenshots, HAR files or Xray-compatible results help investigation and auditing; they are not the same as executable test source. After code export, review selectors, restore omitted behavior and run the test against a known regression.

**Pricing** See vendor pricing for ongoing mabl usage and account for the destination runner's infrastructure.

## Katalon: your tests may already belong in Git

[Katalon Studio's Git integration](https://docs.katalon.com/katalon-studio/manage-projects/project-settings/git-integration/git-integration-in-katalon-studio) supports project versioning, branches and synchronization with hosted Git services. Moving a Studio project into a repository does not inherently require replacing Katalon.

Its [artifact-sharing guide](https://docs.katalon.com/katalon-studio/manage-test-artifacts/test-artifacts-sharing-in-katalon-studio) documents exporting test cases, test objects, profiles and custom keywords through Tools > Utility > Export Test Artifact. An active Studio license is required. The resulting `shared-[timestamp].zip` is documented for import into another Katalon Studio project.

**Keep that path if** you want project source control or sharing between Studio projects.

**Watch for** calling the ZIP a universal importer format. The documented import accepts artifacts exported from Studio. It is not a Playwright, Cypress or Momentic import contract. If you change tools, inspect scripts and referenced objects, then recreate their behavior in the destination. Preserve setup, custom keywords and profiles rather than translating only visible click steps.

**Pricing** See vendor pricing for Studio and execution licenses. A Git repository does not remove the runner's requirements.

## Playwright and Cypress as destinations

[Playwright Test](https://playwright.dev/docs/intro) keeps browser tests and assertions in code. [Cypress](https://docs.cypress.io/app/get-started/why-cypress) provides end-to-end and component testing with tests in your project. Both can be practical destinations when explicit test code is the goal.

**Pick a code-first runner if** your team wants to maintain its assertions, helpers and browser automation directly. mabl's documented Playwright export is a specific starting path; do not generalize it to every source vendor or every step type.

**Watch for** assuming a syntax rewrite preserves semantics. A retry, session cache or network interception can change what a test proves. Keep the old suite active until the replacement verifies the required behavior and still fails on the defects it should catch.

**Pricing** The runners have open-source tooling. Hosted services and infrastructure have separate terms.

## Where Momentic fits

Momentic's [test-portability guide](/docs/get-started/test-portability) describes YAML test files in your own repository. It recommends using a coding agent, MCP and skills to port an existing specification. It does not document a direct importer for testRigor, mabl or Katalon. It also says there is no automatic converter from Playwright, Cypress or Selenium.

The [Playwright migration guide](/docs/guides/migrate/from-playwright) and [Cypress migration guide](/docs/guides/migrate/from-cypress) explain which setup and execution semantics need adaptation. Use those guides if the source is already in either framework. Exporting mabl to Playwright first does not turn the second migration into an automatic conversion.

For dashboard-managed Momentic web tests, `npx momentic import` downloads Momentic tests and their referenced modules. It does not import another vendor's suite. The mobile CLI has no cloud import command.

There is a portability limit on leaving Momentic too. The guide says Momentic ships no exporter. The YAML and its published format are available, but AI actions, semantic checks and maintenance behavior need explicit replacement in another runner. Enterprise customers can ask about a one-time Playwright eject at contract termination; that is not a general automatic export feature.

Web tests run on Chromium only. Mobile runs use local or hosted iOS simulators and Android emulators. Keep unsupported browser or component coverage in its existing runner. See [pricing](/pricing) for current plans.

## A bounded migration example

Start with one flow, such as opening the sign-in form from the landing page. Complete Momentic's [web setup](/docs/quickstart/web), then save `sign-in.test.yaml` using the documented [file format](/docs/core-concepts/file-format):

`fileType: momentic/test/v2 id: migrated-sign-in url: https://preview.example.com steps:  - click: the Sign in button  - assert: The sign-in form is visible`

Replace the URL and expectations with the original flow. Keep its setup and cleanup. This example does not replace an authenticated login test; port those additional actions and assertions if the original covered them.

`npx momentic lint npx momentic run sign-in.test.yaml --upload-results`

The setup guide covers installation, configuration, Chromium and `MOMENTIC_API_KEY` authentication. The portability guide recommends linting before execution. Run both old and new checks against the same build and starting state. Introduce a known failure and confirm the replacement catches it without weakening the expected outcome.

Keep a coverage checklist and mark each port reviewed, not merely generated. Retire the old test only after its replacement preserves the behavior and CI failure policy you need.

## Bottom line

Export before rewriting, preserve the assertions and prove the new suite catches a known defect. Keep useful coverage running during the move. For an exploratory check while you build repository regressions, [try Mo](https://app.momentic.ai/mo).

## FAQ

Can I export mabl tests into files in my repo?    Yes. mabl documents Playwright TypeScript, Selenium IDE and other export formats through its CLI. Browser code exports have unsupported step types. Inspect and repair the result before relying on it as a replacement suite.    Can I export a testRigor suite into files we control?    Yes. testRigor documents testrigor clone for cases, reusable rules and settings, plus CLI loading of file-based inputs. Those files still use testRigor's syntax. Changing the execution engine requires more than committing the export.    Can another tool import Katalon test cases directly?    Katalon's documented artifact ZIP is for sharing between Studio projects. Do not assume another runner accepts it. Preserve the native project in Git, then adapt its behavior if you choose a different runner.    Does Momentic directly import testRigor, mabl or Katalon?    No direct importer is documented in the portability and migration guides. Use the source files and specifications to re-author bounded flows, then verify them. momentic import refers to Momentic dashboard web tests.    Does keeping YAML in Git mean a test runs without Momentic?    No. Source access and runtime independence are different. Replacing Momentic's AI-dependent behavior requires implementation in the destination runner. The published YAML format helps you inspect and port the source; it does not supply another engine.

Still have additional questions?

## Keep reading.

[Resources   How to turn Jira and Linear tickets into end-to-end tests and bug reports automatically     Use Jira and Linear context to scope Mo testing, review findings, file Linear issues and create regression tests with documented integrations.     Wei-Wei Wu     7 min read](/blog/jira-tickets-to-end-to-end-tests)[Resources   How to test a Lovable, Replit or Bolt app before you ship it     Test a Lovable, Replit, Bolt or Claude Code app before release with code checks, browser regressions, authorization tests and CI gates.     Wei-Wei Wu     7 min read](/blog/test-lovable-replit-app-before-deploy)[Resources   Is Browser Use good enough for regression testing?     Compare Browser Use, Stagehand, Playwright and Momentic for regression testing, plus Promptfoo and DeepEval for LLM evaluation.     Wei-Wei Wu     7 min read](/blog/browser-use-regression-testing)

## Try Mo on your app.

Mo is an AI QA engineer. It tests your running app and files each bug with repro steps. Free to start, no credit card.

[Try for free](https://app.momentic.ai/signup) [Contact sales](/sales)
