Migrating From testRigor To KaneAI

---

This guide covers your testRigor migration to KaneAI, the TestMu AI testing agent that builds tests from natural language instructions. The guide covers what to collect from testRigor, where each asset goes on TestMu AI, and how to run the re-created tests.

testRigor tests are written as steps in what testRigor calls "plain English". KaneAI also takes natural language instructions. You re-create each testRigor step as an instruction in a KaneAI session.

[Note: KaneAI does not import or convert testRigor tests. You collect your steps and data with testRigor's own tools, optionally bring test cases into Test Manager, and re-create each test in KaneAI.]

---

What Moves From testRigor and Where It Goes

testRigor asset	Where it goes on TestMu AI	How
Test case steps	KaneAI test cases	Re-create the steps in a KaneAI session
Test case names and steps, for tracking	Test Manager test cases	Build a CSV from the collected steps and import it
Reusable rules	KaneAI modules	Re-create the steps once and save them as a module
Test Data (global variables)	KaneAI variables and secrets	Re-create each value
Data Sets	Datasets in Test Manager	Download as CSV in testRigor, then import in the dataset editor
call api steps	API steps in a KaneAI test	Paste a curl command for the same request
Authenticator-app 2FA	KaneAI TOTP variables	Add the Base32 secret key
Test case files in a repo (.txt, .yaml)	Kane CLI _test.md files	Re-write browser test steps as a Markdown test
Run history and execution reports	Stay in testRigor	Export what you need from testRigor first

Before You Start

• A TestMu AI account with KaneAI access. Create one on the TestMu AI signup page.
• A Test Manager project for the re-created tests and datasets.
• Your TestMu AI username and access key from Account Settings > Password & Security. The testRigor integration and CI runs use them.
• A testRigor account with access to your suites.
• A testRigor Personal Authentication Token. In testRigor, click your username, select API Tokens, and click Generate New Token.
• An MCP client. testRigor's MCP guide covers Claude Code and Cursor.

Step 1: Collect Your testRigor Test Cases and Data

Connect testRigor's MCP server to your MCP client. testRigor documents this command for Claude Code:

Verified

claude mcp add --transport http testrigor https://api2.testrigor.com/api/v1/mcp --header "personal-access-token: <your-token>" -s user

Other MCP clients use the same endpoint with a personal-access-token header. Then use these testRigor tools:

• List test suites lists your test suites.
• List test cases lists the test cases in a suite.
• Get test case returns details such as the description, UUID and steps. Save each test's steps as text.
• List rules and Get rule return your reusable rules.
• List global variables returns what the testRigor UI calls Test Data.
• Get data set returns a data set's full schema and row values.

To save a Data Set as a file, open the Test Data page in testRigor, go to Data Sets, and download it as CSV.

If you keep tests as files for the testRigor CLI, a .txt test case holds only steps, and a .yaml one holds them under customSteps. testRigor's Test Automation Blueprint also mentions exporting YAML or txt files from a suite.

Step 2: Keep Running testRigor Tests on TestMu AI (Optional)

While you re-create tests, testRigor can keep running your existing suite on the TestMu AI cloud through its integration.

1. In testRigor, go to Settings > Integrations. Enable the integration, enter your TestMu AI username and access key, and click Save.
2. Open Settings > Multiple browsers for desktop web, or Settings > Multiple devices for mobile.
3. Select the provider, add browsers or devices, and click Save. testRigor's guide labels the provider LAMBDA_TEST.

For each test case run, testRigor creates one build on TestMu AI per browser or device. See testRigor Integration.

Step 3: Bring Test Cases Into Test Manager (Optional)

testRigor documents CSV exports for Data Sets and run summaries, not test case steps. To load your cases into Test Manager, build the CSV yourself.

1. Create a CSV with one row per test case: the test name in one column and the numbered steps in another.
2. In your Test Manager project, go to Add Test Case > Import CSV.
3. Select Test cases use a single row, where a test case's steps are combined in one row and numbered.
4. Map the name column to Title, which is mandatory, and the steps column to Steps.
5. Map the values, review the preview, and start the import. Each file can be up to 10 MB.

See Import Test Cases from CSV.

Step 4: Re-create Your Tests in KaneAI

Start From a Test Case

Open a saved test case and click Automate with KaneAI in its Automate section. This opens a KaneAI session pre-filled with the test case's steps, where you author the automated test and then execute it. This works on one test case at a time, and the test case must have steps. See Automate with KaneAI.

Start a New Test

You can also start in KaneAI. Match each testRigor suite type to a KaneAI test:

• Desktop Web Testing: create a desktop browser test.
• Mobile Web Testing: create a mobile browser test.
• Native and Hybrid Mobile: for a native Android or iOS app, create an app test and add the app.

Type each testRigor step as a natural language instruction and run it in the session.

Rebuild Rules, Test Data and Data Sets

• Reusable rules: A module groups test steps into one reusable unit. Author and run the rule's steps, pause the session, select them, and click Create Module. Add it to other tests with / and Add Module. See Modules.
• Test Data: Global variables work across test cases in your organization, and environment variables change by environment. Create them with / and Add a variable, or on the Variables page. A step such as Set username as John creates a local variable. See Variables in KaneAI and Secrets.
• Data Sets: In your Test Manager project, open Datasets. Use Import Data in the dataset editor to load the testRigor CSV, verify the data, and save. See Datasets.
• Authenticator-app 2FA: Create a TOTP variable from the Base32 secret key, then use {{totp.variable_name}} in a step. See TOTP Authentication.

Re-create API Steps

Re-create each testRigor call api step as a KaneAI API step. Add an API through the slash command, paste a curl command, and validate it. KaneAI fills in the request details and stores a successful response as a JSON variable. See API Testing.

testRigor API Step

call api get "https://jsonplaceholder.typicode.com/users/10" with headers "Content-Type:application/json" and "Accept:application/json" and get "$..catchPhrase" and save it as "searchWord" and then check that http code is 200

curl Command for KaneAI

curl -X GET "https://jsonplaceholder.typicode.com/users/10" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json"

The curl command covers only the request. Validating it shows the response status. To re-create the value extraction, reference the stored JSON variable in a later step.

Generate Code

KaneAI generates code only for a test saved as Ready, which means every step has run and passed. Framework support depends on the authoring experience:

Framework	Language	Classic	New Experience
Selenium	Python	Available (default)	Not available
Selenium	Java	Available on request	Not available
Playwright	Python	Available on request	Available
Playwright	C#	Available on request	Not available
Playwright	JavaScript	Available on request	Available
Appium	Python	Available (default)	Coming soon

To enable an option marked "Available on request", or the New Experience, contact support. See Code Generation.

Step 5: Run Your KaneAI Tests

1. In your Test Manager project, go to Test Runs, click Create Test Run, and set Type to KaneAI Generated Test Cases.
2. Add test cases. Only test cases with generated code are available.
3. Assign each test case, add configurations, and save the run.
4. Click Run on HyperExecute and choose Run Instances Now or Schedule Test Run.

See Execute Test Runs on HyperExecute.

With the KaneAI toggle on, test run configurations offer Desktop and Real Device. As Configurations states:

• "Native app testing on Real Devices is available only for KaneAI-generated test runs."
• "Virtual Mobile configurations are available for non-KaneAI test runs only."

To trigger a saved run from CI/CD tools such as GitHub Actions or Jenkins, send a POST request with its test run ID to https://test-manager-api.lambdatest.com/api/atm/v1/hyperexecute. Copy the ID from the test run's URL, and authenticate with your TestMu AI username and access key. See Test Automation with CI/CD.

In place of testRigor's localhost tunnel, KaneAI supports tunneling for websites hosted locally or behind a firewall. See Geolocation, Tunnel and Proxy.

What Does Not Carry Over

• Tests, rules and test data. KaneAI does not import or convert testRigor tests. You re-create each test, rule and value.
• Run history and reports. testRigor exports executions as .docx or .pdf files and run summaries as CSV. These stay as files.
• Version history. testRigor's Version History for each test case stays in testRigor.
• Native Windows apps and mainframe tests. testRigor covers native Windows applications in paid versions, and mainframe apps. Code Generation says KaneAI "is available for desktop web applications as well as native mobile applications currently". These tests have no KaneAI target.
• Email, SMS and phone calls. testRigor runs these through its own commands and a Twilio integration. This guide does not map them to KaneAI. TOTP variables generate authenticator-app codes from a shared secret key.- Labels. testRigor labels do not transfer. Add tags when you save each KaneAI test.

Related migration guides

• Import Test Cases from CSV: load test case titles and steps into Test Manager.
• Migration from Katalon: the one-click importer for Katalon Studio desktop web tests.
• Testim To KaneAI Migration: the matching guide for Testim tests.
• mabl To KaneAI Migration: the matching guide for mabl tests.
• Momentic To KaneAI Migration: the matching guide for Momentic tests.
• ACCELQ To KaneAI Migration: the matching guide for ACCELQ tests.