From fd34423f65b1402cbf9de36060c8720c8631b302 Mon Sep 17 00:00:00 2001 From: VishalLT Date: Tue, 22 Sep 2026 21:59:21 +0530 Subject: [PATCH 1/4] old domain link Update --- docs/enterprise-ready.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/enterprise-ready.md b/docs/enterprise-ready.md index a55a19bce..63fe95acd 100644 --- a/docs/enterprise-ready.md +++ b/docs/enterprise-ready.md @@ -410,7 +410,7 @@ TestMu AI supports regional data residency and tenant isolation for regulated de - Org-level secrets management - Priority support SLA -**For pricing details**: [lambdatest.com/pricing](https://www.testmuai.com/pricing/) +**For pricing details**: [testmuai.com/pricing](https://www.testmuai.com/pricing/) --- From 7774941cfcdfd1e1b630e84dff161832a6a63d55 Mon Sep 17 00:00:00 2001 From: VishalLT Date: Fri, 16 Oct 2026 15:38:12 +0530 Subject: [PATCH 2/4] new pages created migrations support docs --- docs/autosana-to-kaneai-migration-guide.md | 347 +++++++++++++ .../browserstack-to-kaneai-migration-guide.md | 395 +++++++++++++++ ...wserstack-to-lambdatest-migration-guide.md | 2 + docs/lambdatest-capability-map.md | 4 +- docs/mabl-to-kaneai-migration-guide.md | 467 ++++++++++++++++++ docs/migrate-appium-tests-from-sauce-labs.md | 3 + docs/migrate-selenium-test-suite.md | 2 + docs/momentic-to-kaneai-migration-guide.md | 414 ++++++++++++++++ docs/one-click-migration-from-katalon.md | 4 + docs/parasoft-to-kaneai-migration-guide.md | 382 ++++++++++++++ docs/saucelabs-to-kaneai-migration-guide.md | 356 +++++++++++++ ...saucelabs-to-lambdatest-migration-guide.md | 1 + docs/tester-army-to-kaneai-migration-guide.md | 411 +++++++++++++++ docs/testim-integration.md | 2 + docs/testim-to-kaneai-migration-guide.md | 338 +++++++++++++ docs/testrigor-integration.md | 4 + docs/testrigor-to-kaneai-migration-guide.md | 351 +++++++++++++ docs/uipath-integration.md | 2 + ...th-test-cloud-to-kaneai-migration-guide.md | 357 +++++++++++++ sidebars.js | 50 ++ 20 files changed, 3890 insertions(+), 2 deletions(-) create mode 100644 docs/autosana-to-kaneai-migration-guide.md create mode 100644 docs/browserstack-to-kaneai-migration-guide.md create mode 100644 docs/mabl-to-kaneai-migration-guide.md create mode 100644 docs/momentic-to-kaneai-migration-guide.md create mode 100644 docs/parasoft-to-kaneai-migration-guide.md create mode 100644 docs/saucelabs-to-kaneai-migration-guide.md create mode 100644 docs/tester-army-to-kaneai-migration-guide.md create mode 100644 docs/testim-to-kaneai-migration-guide.md create mode 100644 docs/testrigor-to-kaneai-migration-guide.md create mode 100644 docs/uipath-test-cloud-to-kaneai-migration-guide.md diff --git a/docs/autosana-to-kaneai-migration-guide.md b/docs/autosana-to-kaneai-migration-guide.md new file mode 100644 index 000000000..ccb3248ad --- /dev/null +++ b/docs/autosana-to-kaneai-migration-guide.md @@ -0,0 +1,347 @@ +--- +id: autosana-to-kaneai-migration-guide +title: How to migrate from Autosana to KaneAI +hide_title: true +sidebar_label: Autosana To KaneAI Migration +description: Plan your Autosana migration to KaneAI. Export flows with the Autosana CLI, import them into Test Manager through CSV, then re-create them as KaneAI tests. +keywords: + - autosana migration to kaneai + - autosana to kaneai migration + - migrate from autosana to kaneai + - how to migrate from autosana to kaneai + - export autosana flows + - autosana flow.yaml +url: https://www.testmuai.com/support/docs/autosana-to-kaneai-migration-guide/ +site_name: TestMu AI +slug: autosana-to-kaneai-migration-guide/ +canonical: https://www.testmuai.com/support/docs/autosana-to-kaneai-migration-guide/ +--- + +import CodeBlock from '@theme/CodeBlock'; +import {YOUR_LAMBDATEST_USERNAME, YOUR_LAMBDATEST_ACCESS_KEY} from "@site/src/component/keys"; + +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; +import BrandName, { BRAND_URL } from '@site/src/component/BrandName'; +import { CookieTrackingSignup } from '@site/src/component/CookieTracking'; +import VerifiedTag from '@site/src/component/verifiedTag'; + + + + + + + + +# Migrating From Autosana To KaneAI +* * * +This guide covers your Autosana migration to KaneAI: exporting your flows, importing them into Test Manager, and re-creating and running them in KaneAI. In Autosana, you write end-to-end tests, called flows, in natural language for mobile apps and websites. KaneAI also builds tests from natural language instructions, so your flow text is a useful starting point. + + +[Note: KaneAI does not import or convert Autosana tests. You export flows with the Autosana CLI and import them into Test Manager through a CSV that you build. Then you re-create each flow in KaneAI.] + + + +*** +## What Moves From Autosana and Where It Goes + +| Autosana asset | Where it goes on | How | +|---|---|---| +| Mobile app flows | KaneAI app tests for Android and iOS | Re-create each flow from its instructions | +| Web flows | KaneAI web tests | Re-create each flow with **Create a Web Test** | +| Flow names and instructions | Test Manager test cases | Build a CSV from the export and import it | +| Suites | Test Manager folders and test runs | Map suite names to folders, then group tests in a test run | +| Suite Auth Instructions | A KaneAI module | Save the login steps as a module and reuse it | +| Variables and environment values | KaneAI variables and secrets | Create them again in KaneAI | +| Hooks | Not carried over | Re-create the setup they perform | +| Automations | Scheduled test runs and CI | Schedule a test run, or start it from CI through the API | +| Real-device runs | KaneAI test runs on real devices | Use a Real Device configuration with the KaneAI toggle on | +| Simulator and emulator runs | Not available for KaneAI test runs | Move that coverage to real devices, or run it with Kane CLI | +| Run history, recordings and Issues | Stay in Autosana | Not part of the export | + + + +## Before You Start + +- **A account.** Create one on the signup page. Copy your username and access key from Account Settings > [Password & Security](https://www.testmuai.com/login/?redirectTo=https://accounts.lambdatest.com/security/username-accesskey). +- **KaneAI and Test Manager access.** **Automate with KaneAI** requires KaneAI access, and test runs live in Test Manager. +- **Your app build.** KaneAI app tests take an APK for Android or an IPA for iOS. Autosana runs an iOS `.app` build on simulators only, so you may need an `.ipa` built for physical devices. +- **The Autosana CLI.** Install it with `curl -fsSL https://get.autosana.ai | sh` or `pipx install autosana`, then run `autosana login`. Autosana's pricing page lists the CLI and tests as code on every plan. +- **An Autosana API key, for the API only.** Create it under **Settings > API Keys** in Autosana, or with `autosana keys create`. + +## Step 1: Export Your Autosana Flows + +Export your dashboard flows to files with the Autosana CLI. These commands come from Autosana's "Migrating Existing Flows" page: + + + +```bash +# Write every dashboard flow, suite, and their hooks to ./.autosana (with explicit keys) +autosana flows export --all + +# Or export a single suite and its flows +autosana flows export --suite "Smoke Tests" +``` + + +The export writes each flow as a `*.flow.yaml` file, each suite as a `_suite.yaml` manifest, and their setup and teardown hooks under `hooks/`. cURL hooks have no file form, so they stay in the Autosana dashboard. + +A flow file needs only `name` and `instructions`. The instructions are one multiline prompt or a list of steps, which Autosana numbers into a single prompt. + +If you prefer JSON, the Autosana List Flows API returns each flow's name and natural language instructions: + + + +```bash +# Get all flows +curl -X GET https://backend.autosana.ai/api/v1/flows \ + -H "X-API-Key: YOUR_API_KEY" +``` + + +The export holds natural language flows and hook files, not framework test code. So there is no exported code to run on the cloud grid. + +## Step 2: Import Flows Into Test Manager + +Test Manager has no importer for Autosana files, but it imports test cases from CSV. Build one CSV from your exported flows, with one flow per row: + +- A title column with the flow `name`. +- A steps column with the instructions, numbered as `1. ... 2. ...` in one cell. +- Optionally, a folder column with the suite name. + +For example, the Autosana flow file below maps to the CSV row in the second tab. + + + + + +```yaml +name: Checkout happy path +setup_hooks: + - seed-db +teardown_hooks: + - reset-test-env +instructions: + - Add an item to the cart and check out + - Verify the order confirmation appears +``` + + + + +```csv +Title,Steps +Checkout happy path,"1. Add an item to the cart and check out 2. Verify the order confirmation appears" +``` + + + + + + +Then import the file: + +1. In your Test Manager project, go to **Add Test Case > Import CSV**. +2. Upload the file and select the **Test cases use a single row** layout. +3. Map your title column to **Title**, which is mandatory, and your steps column to **Steps**. If you added a folder column, map it to **Folder**. +4. Map the values, review the preview, and start the import. + +Each file can be up to 10 MB. See [Import Test Cases from CSV](/support/docs/csv-import/) for the full workflow. + +Autosana references such as `${env:LOGIN_PASSWORD}` are Autosana syntax. To reference a KaneAI variable or secret in a test case step, type `{{` and select it from the list. A pasted environment variable reference is not recognized. Using variables and secrets in test case steps is available on request. See [Use Variables, Parameters, and Secrets in Manual Test Cases and Modules](/support/docs/test-manager-variables-parameters-secrets/). + +## Step 3: Re-create Your Flows in KaneAI + +Re-create each flow as a KaneAI test. You can start from an imported test case or from a new test. + +### Start From a Test Case + +Open an imported 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. It works on one saved test case at a time, and the test case must have steps. + +If the steps use environment variables, choose the environment first. It cannot be changed once the session starts. See [Create & Manage Test Cases](/support/docs/manual-test-case-creation/#automate-with-kaneai). + +### Start a New App Test + +On the KaneAI homepage, click **Create an App Test**. Choose Android or iOS, select a real device, and upload your app. Then write each step in natural language, using your Autosana instructions as a guide. For web flows, click **Create a Web Test** instead. See [App Test](/support/docs/kane-ai-app-test/), [Mobile App Testing Patterns](/support/docs/kaneai-kb-mobile-app-testing-patterns/) and the [app test writing guidelines](/support/docs/kane-ai-app-test-writing-guidelines/). + +[Manual Interaction](/support/docs/kaneai-manual-interaction/) also records actions you perform on the app, such as clicks and typing, as steps. It supports Android apps, and iOS apps in portrait. Verify and assert steps must still be written instructions. + +### Reuse Steps and Data + +- **Modules:** Autosana Auth Instructions run your login once at the start of a suite. In KaneAI, author the login steps once and save them as a [module](/support/docs/kane-ai-modules/). Add it to other tests by typing `/` and selecting **Add Module**. +- **Variables and secrets:** Re-create Autosana variables as KaneAI [variables](/support/docs/kane-ai-using-variables/). Keep passwords and tokens as [secrets](/support/docs/kane-ai-secrets/). + +### Generate Code + +A test saved as **Ready**, where every step has run and passed, generates code. For native app tests, Appium Python is "Available (default)" in Classic and "Coming soon" in New Experience. For web tests, Classic generates Selenium Python by default, and New Experience generates Playwright Python and JavaScript. Other Classic web frameworks are available on request. See [KaneAI Automation Code Generation](/support/docs/kane-ai-automation-code-generation/). + +:::note +With Kane CLI, you write tests as natural language `_test.md` files and commit them to your repository. Kane CLI does not run Autosana `.flow.yaml` files, so you write each test again in that format. For mobile, Kane CLI runs on virtual devices only: the iOS Simulator and the Android Emulator. Local runs need macOS on Apple Silicon, and remote runs need HyperExecute with macOS runners. See [Test.md](/support/docs/kane-cli-testmd/) and [Mobile Testing with Kane CLI](/support/docs/kane-cli-mobile/). +::: + +## Step 4: Run Your KaneAI Tests + +Run KaneAI tests through a test run in Test Manager: + +1. In your project, open **Test Runs** and click **Create Test Run**. Set **Type** to **KaneAI Generated Test Cases**. +2. Add test cases. Only test cases with generated code are available. +3. Assign the test cases and set their configurations. +4. Save the run, click **Run on HyperExecute**, and choose **Run Instances Now** or **Schedule Test Run**. + +See [Execute Test Runs on HyperExecute](/support/docs/kaneai-hyperexecute-test-run-execution/). + +[Configurations in KaneAI & Test Manager](/support/docs/test-runs-configurations/) describes the device scope. With the KaneAI toggle on, the available platforms are Desktop and Real Device. The doc also states: + +- "Native app testing on Real Devices is available only for KaneAI-generated test runs." +- "Mobile browser testing on Real Devices is available for non-KaneAI test runs only." +- "Virtual Mobile configurations are available for non-KaneAI test runs only." + +So in KaneAI test runs, you run your Autosana simulator and emulator coverage on real devices. Selecting several manufacturers, devices and OS versions in one configuration creates a larger device pool. A run can then proceed even if specific devices are unavailable. + +To replace Autosana Automations, click the three dots next to a test run and select **Create Schedule**. See [Scheduled Test Runs](/support/docs/kaneai-scheduled-test-runs/). + +To replace the Autosana GitHub Action, call the test run API from your pipeline. Copy the Test Run ID from the test run URL. Send it in a POST request to `https://test-manager-api.lambdatest.com/api/atm/v1/hyperexecute`. Use your username and access key for Basic Authentication. The response links to the HyperExecute job. See [Test Automation with CI/CD](/support/docs/kaneai-ci-cd-automation/). + +## What Does Not Carry Over + +- **Run history and results.** The export writes flows, suites and hooks only. Run history, recordings and the Issues list stay in Autosana. Its Runs API retrieves run results if you need a record. +- **Hooks.** Script and launch-argument hooks export as files, and cURL hooks stay in the dashboard. KaneAI tests do not run Autosana hooks, so re-create the setup they perform. +- **Autosana syntax in instructions.** References such as `${hooks:...}`, `${file:...}` and `${env:...}`, and actions such as Run Appium Script, belong to Autosana. Rewrite those steps for KaneAI. +- **Run settings.** Run caching, auto-retries, two-device flows and parallel suites are Autosana settings. They do not transfer to KaneAI. For retries in CI, the test run API takes `retry_on_failure` and `max_retries`. + + + +## Related migration guides + +- [Import Test Cases from CSV](/support/docs/csv-import/): bring test cases into Test Manager from a CSV file. +- [Migration from Katalon](/support/docs/one-click-migration-from-katalon/): import Katalon Studio desktop web test cases into KaneAI. +- [testRigor To KaneAI Migration](/support/docs/testrigor-to-kaneai-migration-guide/): move from testRigor to KaneAI. +- [Momentic To KaneAI Migration](/support/docs/momentic-to-kaneai-migration-guide/): move from Momentic to KaneAI. +- [mabl To KaneAI Migration](/support/docs/mabl-to-kaneai-migration-guide/): move from mabl to KaneAI. +- [Tester Army To KaneAI Migration](/support/docs/tester-army-to-kaneai-migration-guide/): move from Tester Army to KaneAI. diff --git a/docs/browserstack-to-kaneai-migration-guide.md b/docs/browserstack-to-kaneai-migration-guide.md new file mode 100644 index 000000000..6aeac2bd4 --- /dev/null +++ b/docs/browserstack-to-kaneai-migration-guide.md @@ -0,0 +1,395 @@ +--- +id: browserstack-to-kaneai-migration-guide +title: How to migrate from BrowserStack to KaneAI +hide_title: true +sidebar_label: BrowserStack To KaneAI Migration +description: Plan your BrowserStack migration to KaneAI. Run scripts and exported Low Code Automation tests on TestMu AI, import test cases, and re-create flows in KaneAI. +keywords: + - browserstack migration to kaneai + - browserstack to kaneai migration + - migrate from browserstack to kaneai + - how to migrate from browserstack to kaneai + - browserstack low code automation export + - browserstack selenium ide export + - browserstack test management csv export +url: https://www.testmuai.com/support/docs/browserstack-to-kaneai-migration-guide/ +site_name: TestMu AI +slug: browserstack-to-kaneai-migration-guide/ +canonical: https://www.testmuai.com/support/docs/browserstack-to-kaneai-migration-guide/ +--- + +import CodeBlock from '@theme/CodeBlock'; +import {YOUR_LAMBDATEST_USERNAME, YOUR_LAMBDATEST_ACCESS_KEY} from "@site/src/component/keys"; + +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; +import BrandName, { BRAND_URL } from '@site/src/component/BrandName'; +import { CookieTrackingSignup } from '@site/src/component/CookieTracking'; +import VerifiedTag from '@site/src/component/verifiedTag'; + + + + + + + +# Migrating From BrowserStack To KaneAI +* * * +This guide covers your BrowserStack migration to KaneAI: how to move your tests to and re-create the flows you want in KaneAI. It covers Selenium and Playwright scripts on Automate, Appium scripts on App Automate, Low Code Automation tests and Test Management test cases. + + +[Note: KaneAI does not import or convert BrowserStack tests. You run scripts and exported Low Code Automation tests on the cloud. Then you import test cases into Test Manager and re-create flows in KaneAI in natural language.] + +To move only Selenium scripts to the grid, see [How to migrate from BrowserStack to ](/support/docs/browserstack-to-testmu-migration-guide/). + + + +*** +## What Moves From BrowserStack and Where It Goes + +| BrowserStack asset | Where it goes on | How | +|---|---|---| +| Selenium and Playwright scripts on Automate | cloud grid | Update the credentials, endpoint and capabilities | +| Appium scripts on App Automate | Appium grid | Update the credentials, hub URL and capabilities | +| Low Code Automation tests | Selenium Grid | Export as Selenium IDE (.side) or Nightwatch.js, then run them | +| Test Management test cases | Test Manager | Export a CSV file, then use CSV import | +| Flows you want as KaneAI tests | KaneAI | Re-create them in natural language or with **Automate with KaneAI** | +| Run history, videos and logs | Stay in BrowserStack | No importer reads them | + + + +## Before You Start + +- **A account.** Create one on the signup page. Your username and access key are under Account Settings > [Password & Security](https://www.testmuai.com/login/?redirectTo=https://accounts.lambdatest.com/security/username-accesskey). +- **[KaneAI](/support/docs/getting-started-with-kane-ai/) and [Test Manager](/support/docs/test-manager/) access.** The **Automate with KaneAI** action requires KaneAI access. +- **The Low Code Automation Pro plan, if you export Low Code Automation tests.** BrowserStack offers the Export Tests feature only on this plan. The export API uses your BrowserStack username and access key. +- **Node.js and npm.** You install the Selenium IDE (SIDE) Runner with npm. BrowserStack's bulk export script also needs jq. + +## Step 1: Export Your BrowserStack Tests + +### Automate and App Automate Scripts + +Your Selenium, Playwright and Appium scripts are already code in your project, so there is nothing to export. + +### Low Code Automation Tests + +Low Code Automation exports recorded tests through its REST API, as Selenium IDE (.side) or Nightwatch.js files. + +Copy a test ID with **Copy test ID** under the **Configurations** section, or list every test with its ID: + + + +```bash +curl -u "YOUR_USERNAME:YOUR_ACCESS_KEY" -X GET "https://lcnc-api.browserstack.com/api/v1/test-list" +``` + +Then download the test. Replace `{test_id}` with the ID. This command saves the test as `test.side`: + + + +```bash +curl -u "YOUR_USERNAME:YOUR_ACCESS_KEY" -X GET "https://lcnc-api.browserstack.com/api/v1/tests/{test_id}/export" -o test.side -L +``` + +For Nightwatch.js, add `?format=nightwatch` to the export URL and save the output as a `.js` file. The default format is `side`. + +To export every test, use the shell script on BrowserStack's **Bulk export tests as code** page. It saves each test as a .side file, then converts the files to code in the language you set: Python, Java, JavaScript, C# or Ruby. On Windows, run it in Git Bash or WSL. + +## Step 2: Run Your Tests on the Cloud + +### Run Automate and App Automate Scripts + +These guides cover the changes for each framework: + +- **Selenium:** [How to migrate from BrowserStack to ](/support/docs/browserstack-to-testmu-migration-guide/) covers credentials, the hub URL and capabilities. +- **Appium:** [Migrate Appium Tests](/support/docs/migrate-appium-tests-from-browserstack-and-saucelabs/) covers authentication, the hub URL and desired capabilities. +- **Playwright:** [How to Migrate Existing Playwright Tests to ](/support/docs/migrate-existing-playwright-tests/) shows how to connect Playwright to the CDP endpoint. +- **Capability names:** the [ Capability Map](/support/docs/testmu-capability-map/) shows BrowserStack and capabilities side by side. + +The scripts keep running as code. They do not become KaneAI tests. + +### Exported Low Code Automation Tests + +Pick the tab for your export format. + + + + + + + +Install the SIDE Runner: + +```bash +npm install -g selenium-side-runner +``` + +Run the file on the Selenium Grid. Put your username and access key in the grid URL: + +```bash +selenium-side-runner -w 4 "test.side" --server https://user-name:access-key@hub.lambdatest.com/wd/hub -c "browserName='chrome' browserVersion='latest' platformName='Windows 10'" +``` + +The `-c` flag passes the capabilities, and `-w` sets the number of parallel processes. Change `browserName`, `browserVersion` and `platformName` to the ones you need. See [Guide to Run Selenium IDE Tests Using ](/support/docs/run-selenium-ide-tests-on-testmu-selenium-cloud-grid/). + +If you converted the files to code, follow [How to Migrate Your Selenium Suite to ](/support/docs/migrate-selenium-test-suite/) instead. + + + + + +Set your credentials: + +
+ +{`export LT_USERNAME="${ YOUR_LAMBDATEST_USERNAME()}" +export LT_ACCESS_KEY="${ YOUR_LAMBDATEST_ACCESS_KEY()}"`} + +
+ +Nightwatch.js reads its grid setup from `nightwatch.conf.js` in the cloned sample project: + +```javascript title="nightwatch.conf.js" reference +https://github.com/LambdaTest/nightwatch-selenium-sample/blob/master/nightwatch.conf.js +``` + +Clone that project, run `npm i`, save your exported files in its `tests` folder, then run `npm run single`. See [Selenium With Nightwatch.js](/support/docs/nightwatch-with-selenium-running-nightwatch-automation-scripts-on-testmu-selenium-grid/) for the sample project and run commands. + + + + + +Before you run a file, replace any secret names and AI prompts in it with real values. Also check validation steps, which BrowserStack's sample exports as an `assert` on an internal variable. + +## Step 3: Bring Test Cases Into Test Manager + +Test Management exports test cases as CSV files, or as .feature files for BDD scenarios. The CSV export works for all test cases. It includes steps, preconditions, expected results and metadata. + +In Test Management, open the folder, select the test cases, click the arrow next to **Export** and choose **Export as CSV**. Choose CSV for BDD test cases too, because the Test Manager import reads `.csv` files. BrowserStack recommends .feature files for BDD test cases, so check that your CSV includes the scenarios. + +Then import the file: + +1. In your Test Manager project, go to **Add Test Case > Import CSV**. +2. Pick **Test cases use a single row** or **Test cases use multiple rows**, to match your file. +3. Map the CSV headers to fields. Mapping at least one CSV header to **Title** is mandatory. Steps, outcomes, BDD scenarios, folders and custom fields are optional, but **Automate with KaneAI** needs steps or scenarios. +4. Map the values, review the preview, and start the import. + +Create any custom fields and link them to the project before you import. Each file can be up to 10 MB. See [Import Test Cases from CSV](/support/docs/csv-import/). + +## Step 4: Re-create Your Flows in KaneAI + +KaneAI does not import or convert BrowserStack tests, so you re-create the flows you want to keep. + +### Start From a Test Case + +Open an imported test case and click **Automate with KaneAI** in its **Automate** section. A KaneAI session opens, pre-filled with the test case's steps, where you author and execute the test. KaneAI reads manual steps and `Given` / `When` / `Then` scenarios directly. The action works on one test case at a time, and the test case must have steps or scenarios. See [Create & Manage Test Cases](/support/docs/manual-test-case-creation/#automate-with-kaneai). + +### Start a New Test + +On the KaneAI dashboard, click **Author Browser Test** or **Author App Test** and set up the session. Then describe each step in natural language. See [Author Your First Desktop Browser Test](/support/docs/author-your-first-desktop-browser-test/) and [Author Your First Mobile App Test](/support/docs/author-your-first-mobile-app-test/). + +[Manual Interaction](/support/docs/kaneai-manual-interaction/) records your clicks, typing, scrolling and navigation as steps. It works in desktop browsers, Android apps and iOS apps in portrait, but not in mobile browsers. It cannot record hovers or checks, so write verify and assert steps as instructions. + +While you author, you can also use these features: + +- **Reusable steps and data:** save repeated steps as a [module](/support/docs/kane-ai-modules/), and keep test data in [variables](/support/docs/kane-ai-using-variables/). +- **Single steps:** **Run This Step** in the [authoring session](/support/docs/kaneai-authoring-session/#run-this-step) runs one step. The run actions are available on request and partially rolled out. + +### Rebuild What Did Not Export + +- **Visual checks:** add a **Visual Comparison** step from the `/` menu. See [Visual Test Creation with KaneAI](/support/docs/kaneai-smartui-visual-testing/). +- **API calls:** add an API step with the slash command and paste a curl command. See [KaneAI - API Testing](/support/docs/kane-ai-api-testing/). +- **Secrets:** create [KaneAI secrets](/support/docs/kane-ai-secrets/) and reference them with double curly braces. + +### Generate Code + +A test saved as **Ready**, where every step has run and passed, generates code. The options depend on the authoring experience. New Experience is being rolled out in phases. Contact support to enable New Experience or any option marked available on request. + +| 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 | + +See [KaneAI Automation Code Generation](/support/docs/kane-ai-automation-code-generation/) for the full list. + +## Step 5: Run Your KaneAI Tests + +1. In your project, open **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 the test cases and set their configurations. +4. Save the run, click **Run on HyperExecute**, and choose **Run Instances Now** or **Schedule Test Run**. + +See [Execute Test Runs on HyperExecute](/support/docs/kaneai-hyperexecute-test-run-execution/). + +With the KaneAI toggle on, test runs offer Desktop and Real Device configurations. [Configurations in KaneAI & Test Manager](/support/docs/test-runs-configurations/) also states: + +- "Native app testing on Real Devices is available only for KaneAI-generated test runs." +- "Mobile browser testing on Real Devices is available for non-KaneAI test runs only." +- "Virtual Mobile configurations are available for non-KaneAI test runs only." + +To start a test run from CI, such as GitHub Actions or Jenkins, copy its Test Run ID from the test run URL. Send it in a POST request to `https://test-manager-api.lambdatest.com/api/atm/v1/hyperexecute`, with your username and access key for Basic Authentication. See [Test Automation with CI/CD](/support/docs/kaneai-ci-cd-automation/). + +## What Does Not Carry Over + +- **Run history and results.** No importer reads BrowserStack builds, session videos or logs. +- **Secret values and AI-generated test data.** The Low Code Automation export replaces them with secret names and AI prompts. +- **AI healing.** Low Code Automation's element selection with AI healing is not exported. KaneAI-generated scripts that run on HyperExecute use [Auto-Heal](/support/docs/kaneai-auto-heal/) instead. +- **Visual Validation, API and Open Email steps.** BrowserStack does not currently export them. Step 4 shows how to rebuild visual checks and API calls. +- **Unsupported step types.** BrowserStack's sample .side response shows one as an `echo` command reading "This step type is currently not supported". Search your files for that text. +- **Mobile browser tests in KaneAI test runs.** See the device scope in Step 5. + + + +## Related migration guides + +- [BrowserStack To Migration](/support/docs/browserstack-to-testmu-migration-guide/): move Selenium tests to the grid. +- [Migrate Appium Tests](/support/docs/migrate-appium-tests-from-browserstack-and-saucelabs/): move Appium suites from BrowserStack or Sauce Labs. +- [Sauce Labs To KaneAI Migration](/support/docs/saucelabs-to-kaneai-migration-guide/): move from Sauce Labs to KaneAI. +- [Import Test Cases from CSV](/support/docs/csv-import/): bring test cases into Test Manager. +- [Migration from Katalon](/support/docs/one-click-migration-from-katalon/): import Katalon Studio desktop web tests into KaneAI. +- [Parasoft To KaneAI Migration](/support/docs/parasoft-to-kaneai-migration-guide/): move from Parasoft to KaneAI. diff --git a/docs/browserstack-to-lambdatest-migration-guide.md b/docs/browserstack-to-lambdatest-migration-guide.md index b1998e21e..903ab5c15 100644 --- a/docs/browserstack-to-lambdatest-migration-guide.md +++ b/docs/browserstack-to-lambdatest-migration-guide.md @@ -181,6 +181,8 @@ import VerifiedTag from '@site/src/component/verifiedTag'; [Note: This guide covers the migration of tests running on the cloud grid that uses Selenium 4 and Selenium 3] +To run Low Code Automation tests, import Test Management test cases or re-create flows in KaneAI, see the [BrowserStack to KaneAI migration guide](/support/docs/browserstack-to-kaneai-migration-guide/). + ## Authentication Firstly, you need to change the authentication in your configuration settings of your test suite. For running tests on Selenium Grid, you need to have a valid user_name and access_key to perform tests on our Grid. In case you do not have an account on , visit the signup page and create a new account. + + + + +## Before You Start + +- **A account with KaneAI access.** The **Automate with KaneAI** action requires it. Create one on the signup page. +- Your Username and Access Key, from Account Settings > [Password & Security](https://www.testmuai.com/login/?redirectTo=https://accounts.lambdatest.com/security/username-accesskey). +- Node.js for the mabl CLI. mabl requires an actively supported Node.js LTS version, currently 22 or higher. It does not support running its CLI from Windows Subsystem for Linux (WSL). + +## Step 1: Export Your mabl Tests + +`mabl tests export` exports a mabl test as Playwright (TypeScript), Selenium IDE, JSON, CSV or YAML. YAML is the default. The Playwright and Selenium IDE formats are only supported for browser tests. + +Install the mabl CLI, log in, and list your tests. `mabl auth login --auto` opens the mabl login page in your browser. `mabl tests list` returns test IDs, 10 tests by default. Set `--limit` to list more. + + + +```bash +npm install -g @mablhq/mabl-cli +mabl auth login --auto +mabl tests list +``` + + + + + + +Export each test in the format you plan to run: + + + + + + + +```bash +mabl tests export {test-id} --format playwright --environment-id {environment-id} +``` + +`--environment-id` generates selectors from the find information mabl learned in that environment. `mabl environments list` returns environment IDs. + + + + + +```bash +mabl tests export {test-id} --format side +``` + + + + + + + + +The file goes to your present working directory, named after the test ID, unless you set `--file`. If you plan to import test cases in Step 3, also export each test with `--format csv`. + +## Step 2: Run the Exported Tests on + +These runs are not KaneAI tests. Their results appear on the [ Web Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build). Some mabl step types are not supported in these exports, as listed in [What Does Not Carry Over](#what-does-not-carry-over). + +Set your credentials as environment variables: + + + + + + + +
+ + {`export LT_USERNAME="${ YOUR_LAMBDATEST_USERNAME()}" +export LT_ACCESS_KEY="${ YOUR_LAMBDATEST_ACCESS_KEY()}"`} + +
+ + + + + +
+ + {`set LT_USERNAME=${ YOUR_LAMBDATEST_USERNAME()} +set LT_ACCESS_KEY=${ YOUR_LAMBDATEST_ACCESS_KEY()}`} + +
+ + + + + + + + + + + +mabl's docs do not describe the structure of the Playwright export. For TypeScript tests that use the Playwright test runner, see [How to Run TypeScript Tests With Playwright](/support/docs/typescript-with-playwright/). Its `lambdatest-setup.ts` fixture makes the CDP connection. + +Where your test launches a local browser, connect to the CDP endpoint instead. The `capabilities` object selects the browser and OS. Sample from [How to Migrate Existing Playwright Tests](/support/docs/migrate-existing-playwright-tests/): + +```js +const { chromium } = require('playwright') +const { expect } = require('@playwright/test'); + +(async () => { + const capabilities = { + 'browserName': 'Chrome', // Browsers allowed: `Chrome`, `MicrosoftEdge`, `pw-chromium`, `pw-firefox` and `pw-webkit` + 'browserVersion': 'latest', + 'LT:Options': { + 'platform': 'Windows 10', + 'build': 'Playwright Sample Build', + 'name': 'Playwright Sample Test', + 'user': process.env.LT_USERNAME, + 'accessKey': process.env.LT_ACCESS_KEY, + } + } + + const browser = await chromium.connect({ + wsEndpoint: `wss://cdp.lambdatest.com/playwright?capabilities=${encodeURIComponent(JSON.stringify(capabilities))}` + }) + + // Test code ... + + await browser.close() +})() +``` + + + + + +Install the SIDE Runner: + +```bash +npm install -g selenium-side-runner +``` + +Run the exported file on the Selenium grid. Replace `user-name`, `access-key` and `.side` with your values: + +```bash +selenium-side-runner -w 4 ".side" --server https://user-name:access-key@hub.lambdatest.com/wd/hub -c "browserName='chrome' browserVersion='latest' platformName='Windows 10'" +``` + +`-w` sets the number of parallel processes. `-c` sets the browser, version and platform. See [Run Selenium IDE Tests](/support/docs/run-selenium-ide-tests-on-testmu-selenium-cloud-grid/). + + + + + +## Step 3: Import Test Cases Into Test Manager + +Test Manager has no mabl importer, so use CSV import. mabl's export docs do not list the CSV columns, so open the file and check them first. + +1. In your Test Manager project, go to **Add Test Case > Import CSV**. +2. Choose **Test cases use a single row** or **Test cases use multiple rows**, to match how the steps are laid out. +3. Map the CSV headers to Test Manager fields. Mapping at least one CSV header to **Title** is mandatory. **Steps**, **Outcome**, **Folder**, system fields and custom fields are optional. Leave other columns as **Ignore Field**. +4. Map the values, review the preview, and start the import. + +Each file can be up to 10 MB. See [Import Test Cases from CSV](/support/docs/csv-import/). + +If the columns do not map well, attach the CSV or JSON export to the [AI Test Case Generator](/support/docs/generate-test-cases-with-ai/) instead. It writes new test cases from the file rather than importing the mabl tests. + +## Step 4: Re-create Your Tests in KaneAI + +### Start From a Test Case + +Open a saved test case and click **Automate with KaneAI** in the **Automate** section. KaneAI opens a session pre-filled with the test case's steps, where you author and run the test. This works one test case at a time, and the test case must have steps or scenarios ([Automate with KaneAI](/support/docs/manual-test-case-creation/#automate-with-kaneai)). + +### Start a New Test + +On the KaneAI homepage, click **Create a Web Test** and write each step in natural language ([Author your First Test](/support/docs/kane-ai-web-test/)). For mabl mobile tests, click **Create an App Test** and upload your Android or iOS app ([App Test](/support/docs/kane-ai-app-test/)). + +[Manual Interaction](/support/docs/kaneai-manual-interaction/) records your clicks, typing and scrolling as steps. It works in desktop web browsers, Android apps and iOS apps in portrait, but not in mobile browsers. Add verify or assert steps as written instructions. + +### Rebuild Flows, Variables and DataTables + +- **Flows** are reusable sets of steps in mabl. In KaneAI, select the steps in a paused session and click **Create Module**. Reuse it with **Add Module** from the slash command menu ([Modules](/support/docs/kane-ai-modules/)). +- **Variables:** use **Add a variable** from the slash command menu, or write `Set username as John` in natural language ([Variables in KaneAI](/support/docs/kane-ai-using-variables/)). +- **DataTables:** export each one with `mabl datatables export {datatable-id}` and the `--format csv` option. In Test Manager, open **Datasets**, use **Import Data** in the dataset editor, then verify the data and save ([Datasets](/support/docs/kane-ai-using-datasets/)). + +### Re-create Unsupported Step Types + +mabl's Selenium and Playwright exports do not support these step types. The KaneAI docs below cover each one: + +| mabl step | KaneAI doc | +|---|---| +| Select steps | [Forms, Inputs & Data Entry](/support/docs/kaneai-kb-forms-inputs-and-data-entry/) | +| Drag and drop steps | [Drag and Drop](/support/docs/kane-ai-drag-drop/) | +| JavaScript snippets | [JavaScript Execution](/support/docs/kane-ai-javascript-execution/) | +| API steps | [API Testing](/support/docs/kane-ai-api-testing/) | +| File uploads | [Upload and Download Files](/support/docs/kaneai-upload-and-download-files/) | +| MFA authenticator (TOTP) steps | [TOTP Authentication](/support/docs/kaneai-totp/) | +| Conditional steps (Selenium exports) | [Conditional Logic](/support/docs/kaneai-conditional-logic/) | +| Accessibility checks | **Accessibility Testing** in a Classic report test run, desktop Chrome and Edge only ([Advanced Configurations](/support/docs/kaneai-hyperexecute-test-run-execution/#advanced-configurations)) | + + + + + +### Re-create API Tests + +mabl exports API tests as Postman collections in JSON, from the test details page or the API test editor. KaneAI documents curl input for API steps, not a Postman collection import. To move each request: + +1. Import the mabl JSON file into Postman as a new collection. +2. Open the request, click **Code**, and choose **cURL**. +3. In a KaneAI test, add an API step through the slash command and paste the curl command. You can paste several curl commands to add them all ([API Testing](/support/docs/kane-ai-api-testing/)). + +### Generate Code + +KaneAI generates code for tests saved as **Ready**, where every step has run and passed ([Code Generation](/support/docs/kane-ai-automation-code-generation/)): + +- **Classic:** Selenium Python and Appium Python by default. Selenium Java and Playwright Python, C# and JavaScript are available on request. +- **New Experience:** Playwright Python and Playwright JavaScript. New Experience is rolling out in phases. + +Contact support to enable an on-request framework or New Experience. + +## Step 5: Run Your KaneAI Tests + +1. In your Test Manager project, open **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 team members and update configurations as required, then save the test run. +4. Click **Run on HyperExecute**, then **Run Instances Now** or **Schedule Test Run**. + +See [Execute Test Runs on HyperExecute](/support/docs/kaneai-hyperexecute-test-run-execution/). Device scope, per [Configurations](/support/docs/test-runs-configurations/): + +- With the **KaneAI** toggle on, the available platforms are Desktop and Real Device. +- Native app testing on Real Devices is available only for KaneAI-generated test runs. +- Mobile browser testing on Real Devices is available for non-KaneAI test runs only. +- Virtual Mobile configurations are available for non-KaneAI test runs only. + +For CI tools such as GitHub Actions or Jenkins, copy the Test Run ID from the test run URL. Send it as `test_run_id` in a POST request to `https://test-manager-api.lambdatest.com/api/atm/v1/hyperexecute`, with Basic Authentication ([Test Automation with CI/CD](/support/docs/kaneai-ci-cd-automation/)). + +## What Does Not Carry Over + +- **The tests.** KaneAI does not import or convert mabl tests, and Test Manager has no mabl importer. KaneAI imports tests only from Katalon, for desktop web tests ([Migration from Katalon](/support/docs/one-click-migration-from-katalon/)). Test Manager's one-click importers cover TestRail, qTest, Xray and Zephyr Scale. +- **mabl-generated tests.** Only user-generated tests export. The visit home page, link crawler and visual smoke tests do not. +- **Some steps.** Select steps, drag and drop steps, JavaScript snippets, API steps, cookie interactions and file uploads are not supported in Selenium or Playwright exports. The same applies to download assertions, accessibility checks, MFA authenticator steps, email testing and PDF testing. Selenium exports also do not support conditional steps. +- **Code for other test types.** Playwright and Selenium IDE exports cover browser tests only. +- **Run history and results.** documents no importer for them. Before you leave mabl, export run artifacts with `mabl test-runs export {run-id} --types all`. This works for browser tests run in the mabl cloud. **Coverage > Overview** can also download a CSV of passed and failed test totals by date. + + + +## Related migration guides + +- [Migration from Katalon](/support/docs/one-click-migration-from-katalon/): Katalon desktop web tests into KaneAI. +- [Import Test Cases from CSV](/support/docs/csv-import/): CSV mapping in Test Manager. +- [How to Migrate Existing Playwright Tests to ](/support/docs/migrate-existing-playwright-tests/): the CDP endpoint. +- [Guide to Run Selenium IDE Tests Using ](/support/docs/run-selenium-ide-tests-on-testmu-selenium-cloud-grid/): the SIDE Runner. +- [Testim To KaneAI Migration](/support/docs/testim-to-kaneai-migration-guide/): move from Testim to KaneAI. +- [Momentic To KaneAI Migration](/support/docs/momentic-to-kaneai-migration-guide/): move from Momentic to KaneAI. +- [testRigor To KaneAI Migration](/support/docs/testrigor-to-kaneai-migration-guide/): move from testRigor to KaneAI. +- [Tester Army To KaneAI Migration](/support/docs/tester-army-to-kaneai-migration-guide/): move from Tester Army to KaneAI. +- [Autosana To KaneAI Migration](/support/docs/autosana-to-kaneai-migration-guide/): move from Autosana to KaneAI. diff --git a/docs/migrate-appium-tests-from-sauce-labs.md b/docs/migrate-appium-tests-from-sauce-labs.md index 3b87ac88d..eb025cac6 100644 --- a/docs/migrate-appium-tests-from-sauce-labs.md +++ b/docs/migrate-appium-tests-from-sauce-labs.md @@ -551,6 +551,9 @@ def run_session(desired_cap): driver = webdriver.Remote(command_executor="https://LT_USERNAME:LT_ACCESS_KEY@mobile-hub.lambdatest.com/wd/hub", desired_capabilities=desired_cap) ``` + +To re-create your Appium flows as KaneAI app tests in natural language, follow the [Sauce Labs to KaneAI migration guide](/support/docs/saucelabs-to-kaneai-migration-guide/). + >That’s all about Sauce Labs to migration. In case you have any questions or need any additional information, you could reach out at our  window.openLTChatWidget()}>**24X7 Chat Support** or mail us directly at support@testmuai.com. diff --git a/docs/migrate-selenium-test-suite.md b/docs/migrate-selenium-test-suite.md index c8fd7765d..a351db5c2 100644 --- a/docs/migrate-selenium-test-suite.md +++ b/docs/migrate-selenium-test-suite.md @@ -262,6 +262,8 @@ If you are moving from BrowserStack or Sauce Labs, use these dedicated migration - [Migrate from BrowserStack to TestMu AI](/support/docs/browserstack-to-testmu-migration-guide/) - hub URL, capability mapping, and feature equivalents - [Migrate from Sauce Labs to TestMu AI](/support/docs/saucelabs-to-testmu-migration-guide/) - hub URL, capability mapping, and feature equivalents +Running Parasoft Selenic tests? The [Parasoft to KaneAI migration guide](/support/docs/parasoft-to-kaneai-migration-guide/) shows how to run them on the grid with Selenic still attached, and how to re-create them in KaneAI. + ## Prerequisites --- diff --git a/docs/momentic-to-kaneai-migration-guide.md b/docs/momentic-to-kaneai-migration-guide.md new file mode 100644 index 000000000..3b3cebdb4 --- /dev/null +++ b/docs/momentic-to-kaneai-migration-guide.md @@ -0,0 +1,414 @@ +--- +id: momentic-to-kaneai-migration-guide +title: How to migrate from Momentic to KaneAI +hide_title: true +sidebar_label: Momentic To KaneAI Migration +description: Plan your Momentic migration to KaneAI. Collect your YAML tests, run any ejected Playwright code on TestMu AI, and re-create each test in natural language. +keywords: + - momentic migration to kaneai + - momentic to kaneai migration + - migrate from momentic to kaneai + - how to migrate from momentic to kaneai + - momentic yaml tests to kaneai +url: https://www.testmuai.com/support/docs/momentic-to-kaneai-migration-guide/ +site_name: TestMu AI +slug: momentic-to-kaneai-migration-guide/ +canonical: https://www.testmuai.com/support/docs/momentic-to-kaneai-migration-guide/ +--- + +import CodeBlock from '@theme/CodeBlock'; +import {YOUR_LAMBDATEST_USERNAME, YOUR_LAMBDATEST_ACCESS_KEY} from "@site/src/component/keys"; + +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; +import BrandName, { BRAND_URL } from '@site/src/component/BrandName'; +import { CookieTrackingSignup } from '@site/src/component/CookieTracking'; +import VerifiedTag from '@site/src/component/verifiedTag'; + + + + + + + +# Migrating From Momentic To KaneAI +* * * +This guide covers your Momentic migration to KaneAI: how to re-create your end-to-end tests and run them on . KaneAI is the testing agent that authors web and mobile tests from natural language. + + +[Note: KaneAI does not import or convert Momentic tests. This guide follows a manual path. You keep your Momentic YAML files as the reference and run any Playwright code from Momentic on . Then you re-create each test in KaneAI in natural language.] + + + +*** +## What Moves From Momentic and Where It Goes + +| Momentic asset | Where it goes on | How | +|---|---|---| +| Web tests (`*.test.yaml`) | KaneAI web tests | Re-create each test in natural language | +| Mobile tests (`momentic-mobile`) | KaneAI app tests | Upload your app, then re-create the steps | +| Modules (`*.module.yaml`) | [KaneAI modules](/support/docs/kane-ai-modules/) | Save authored steps as a module | +| Environments, variables and secrets | [KaneAI variables](/support/docs/kane-ai-using-variables/) and [secrets](/support/docs/kane-ai-secrets/) | Re-create the values | +| `assert` steps | [Natural-language assertions](/support/docs/kaneai-kb-assertions-and-validation/) | Write each check as an assertion | +| `if` and `while` steps | [If / Else-If / Else blocks](/support/docs/kaneai-conditional-logic/) and [While Loops](/support/docs/kaneai-while-loops/) | Insert them from the `/` menu. If **While Loop** is missing, ask Support to enable it | +| `javascript` steps | [JavaScript steps](/support/docs/kane-ai-javascript-execution/) | Paste page-level code, and rework Node sandbox code | +| `request` steps | [API steps](/support/docs/kane-ai-api-testing/) | Rewrite each request as a curl command and paste it | +| `visualDiff` steps | [Visual Comparison steps](/support/docs/kaneai-smartui-visual-testing/) | Add the step; its first run sets a baseline | +| Playwright code from an Enterprise eject | cloud grid | Connect to the CDP endpoint | + + + + + + + +## Before You Start + +You need: + +- A account. Create one on the signup page. +- KaneAI access, which the **Automate with KaneAI** action requires. +- Your username and access key, from Account Settings > [Password & Security](https://www.testmuai.com/login/?redirectTo=https://accounts.lambdatest.com/security/username-accesskey). +- For Kane CLI, Google Chrome, plus Node.js 18 or higher for an npm install ([Installing Kane CLI](/support/docs/kane-cli-installation/)). +- The Momentic CLI with an existing project config, signed in with `momentic login` or `MOMENTIC_API_KEY`. It requires Node.js 22.12.0 or later in the 22.x line, or 24.0.0 or later. If you have no project config, the Momentic onboarding wizard (`npx @momentic/wizard@latest`) creates one. +- For Playwright code, a Momentic Enterprise contract. Enterprise customers can ask for a one-time eject at contract termination. +- For KaneAI app tests, your app as an APK for Android or an IPA for iOS. KaneAI test runs put native apps on Real Devices. + +## Step 1: Collect Your Momentic Test Files + +Momentic tests and modules are `*.test.yaml` and `*.module.yaml` files in your repository. Momentic ships no exporter, and those files need none. + +To pull web tests that are still managed in the Momentic dashboard into your repository, run `momentic import` from the web project root: + + + +```bash +npx momentic import +``` + +With no arguments, it imports the workspace's web tests, their referenced modules and environments. It skips mobile tests and unused standalone modules. Imported environment variables can contain plaintext secrets, so move them to runtime secrets before you commit. Mobile tests use the separate `momentic-mobile` CLI, which has no cloud import command. + +To build your inventory, list the test files. Each command prints one path per line. + + + +```bash +npx momentic list +npx momentic-mobile list +``` + + + + +## Step 2: Run Ejected Playwright Code on + +Enterprise customers can ask their Momentic account team for a one-time eject to open-source Playwright at contract termination. Otherwise, skip this step. + +If the code launches a local browser with `chromium.launch`, replace that call with a connection to the CDP endpoint. Set `LT_USERNAME` and `LT_ACCESS_KEY` to your username and access key first. + + + +```javascript +const { chromium } = require('playwright') +const { expect } = require('@playwright/test'); + +(async () => { + const capabilities = { + 'browserName': 'Chrome', // Browsers allowed: `Chrome`, `MicrosoftEdge`, `pw-chromium`, `pw-firefox` and `pw-webkit` + 'browserVersion': 'latest', + 'LT:Options': { + 'platform': 'Windows 10', + 'build': 'Playwright Sample Build', + 'name': 'Playwright Sample Test', + 'user': process.env.LT_USERNAME, + 'accessKey': process.env.LT_ACCESS_KEY, + } + } + + const browser = await chromium.connect({ + wsEndpoint: `wss://cdp.lambdatest.com/playwright?capabilities=${encodeURIComponent(JSON.stringify(capabilities))}` + }) + + // Test code ... + + await browser.close() +})() +``` + +The `capabilities` object selects the browser, browser version and platform, and the comment lists the allowed browser names. See [How to Migrate Existing Playwright Tests](/support/docs/migrate-existing-playwright-tests/), [Playwright With Python](/support/docs/python-with-playwright/) and [Playwright Test Runner](/support/docs/playwright-test-runner/). + +## Step 3: Re-create Your Tests in KaneAI + +Re-create each Momentic test as a new KaneAI test written in natural language. Keep your Momentic suite running until each replacement covers the same checks. + +### Start a New Test + +Open [KaneAI](https://www.testmuai.com/login/?redirectTo=https://kaneai.lambdatest.com/objective) and click **Create a Web Test**. For a mobile app, click **Create an App Test**, select Android or iOS, and upload your app. Write each YAML step as an instruction, such as `Click the Checkout button`, then save the test to a project and folder. + +Write each `assert` step as a natural-language assertion, such as `assert "Your order has been placed" is displayed`. Momentic AI actions describe a goal rather than steps. KaneAI's guidance is that more specific instructions give more accurate tests, so break each goal into explicit steps. See the [web test](/support/docs/kane-ai-web-test/) and [app test](/support/docs/kane-ai-app-test/) guides. + +### Start From a Test Case + +You can also start in Test Manager. Create a test case, add each YAML step as a test step with its check as the expected result, and save it. Then click **Automate with KaneAI** in the test case's **Automate** section. KaneAI opens a session pre-filled with the steps, where you author and run the test. The action works on one saved test case at a time, and the test case needs steps. See [Automate with KaneAI](/support/docs/manual-test-case-creation/#automate-with-kaneai). + +### Rebuild Modules, Variables and Secrets + +Re-create each Momentic module as a KaneAI module. Author the steps, pause the session, select the steps and click **Create Module**. In other tests, type `/` and select **Add Module**. Modules support variables, parameters and secrets. + +A Momentic environment holds a base URL and variables. Re-create those values as KaneAI [environment variables](/support/docs/kane-ai-using-variables/#environments). Selecting an environment before an authoring session starts is available on request, so ask Support to enable it. Store passwords and tokens as [KaneAI secrets](/support/docs/kane-ai-secrets/). + +### Keep Tests in Your Repository With Kane CLI + +If your team keeps tests next to the code, [Kane CLI](/support/docs/kane-cli-testmd/) stores tests as `_test.md` Markdown files that you commit. Each `##` heading marks a step, and the agent reads the natural-language text under it. Kane CLI does not read Momentic YAML as a test, so you rewrite each step. + + + + + +```yaml +fileType: momentic/test/v2 +id: silver-river-lantern +url: https://shop.example.com +steps: + - click: Checkout + - type: + text: jeff@example.com + into: Email input + - assert: An order confirmation is visible +``` + + + + + + + +```markdown +--- +mode: testing +url: https://shop.example.com +--- + +# Checkout confirmation + +## Start checkout +Click the Checkout button. + +## Enter the email +Type "jeff@example.com" into the Email input. +Verify an order confirmation is visible. +``` + + + + + +Run it with `kane-cli testmd run checkout_test.md --agent`. The first run authors each step and saves a recording, and later runs replay from cache. Shared flows, such as a login, go in helper files pulled in with [`@import`](/support/docs/kane-cli-testmd-composition/). + +Kane CLI runs web tests in Chrome. It runs app tests on an Android Emulator or iOS Simulator, on macOS Apple Silicon or on the HyperExecute grid with `kane-cli testrun run --remote`. A remote run needs a plan that includes HyperExecute, with macOS runner concurrency, and the `remote-execution` plugin. See [Remote runs on the cloud grid](/support/docs/kane-cli-remote-execution/). + +In Kane CLI 0.6.1 or later, `kane-cli context ingest` also accepts `.yaml` and `.yml` files as requirement sources. `kane-cli context extract` then proposes use-cases that cite the file's lines, and it consumes credits. From Kane CLI 0.7.1, ingest in a terminal continues straight into extraction. This gives the agent context for new tests. It does not import the Momentic test. See [Requirement Sources](/support/docs/kane-cli-assurance-sources/). + +### Generate Code + +KaneAI generates code for a test saved as **Ready**, where every step has run and passed. The frameworks available depend on the authoring experience: + +| Framework and 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 | + +"Available on request" means you ask Support to enable it. To save the code, click **Download** on the test's **Code** tab. Kane CLI exports Playwright code in Python or JavaScript with `--code-export`, after a successful upload to Test Manager. See [KaneAI Automation Code Generation](/support/docs/kane-ai-automation-code-generation/) and [Kane CLI code export](/support/docs/kane-cli-tms-integration/#code-export). + +## Step 4: Run Your KaneAI Tests + +Momentic runs web tests on Chromium, Google Chrome or Chrome for Testing, and mobile tests on emulators and simulators. On , KaneAI test runs execute on HyperExecute against the configurations you choose. + +### Create a Test Run on HyperExecute + +1. In Test Manager, open your project's test runs and click **Create Test Run**. +2. Choose **KaneAI Generated Test Cases** as the type. +3. Add test cases that have generated code, then assign people and configurations. +4. Save the run, click **Run on HyperExecute**, and choose **Run Instances Now** or **Schedule Test Run**. + +With the **KaneAI** toggle on, configurations offer the **Desktop** and **Real Device** platforms. Desktop configurations cover browsers such as Chrome, Firefox, Safari and Edge. Native app testing on Real Devices is available only for KaneAI-generated test runs. Mobile browser testing on real devices, and Virtual Mobile configurations, are available for non-KaneAI test runs only. See [Configurations](/support/docs/test-runs-configurations/) and [Execute Test Runs on HyperExecute](/support/docs/kaneai-hyperexecute-test-run-execution/). + +### Trigger Test Runs From CI + +To start a saved test run from GitHub Actions, Jenkins or another CI tool, copy the test run ID from its URL. Then call the Test Manager API with Basic Authentication from your username and access key: + +```bash +curl --location 'https://test-manager-api.lambdatest.com/api/atm/v1/hyperexecute' \ +--header 'Content-Type: application/json' \ +--header 'Authorization: Basic ' \ +--data '{ + "test_run_id": "YOUR_TEST_RUN_ID", + "concurrency": 1 +}' +``` + +The response returns links to the HyperExecute jobs. For apps on localhost or behind a firewall, start a [ Tunnel](/support/docs/kane-ai-geolocation-tunnel-proxy/#tunnel-support) and pass its name in the `tunnel` parameter. See [Automating Test Runs Execution with CI/CD](/support/docs/kaneai-ci-cd-automation/). + +## What Does Not Carry Over + +- **Test source.** KaneAI and Kane CLI do not import or convert Momentic YAML. KaneAI imports tests only from Katalon, for desktop web tests ([Migration from Katalon](/support/docs/one-click-migration-from-katalon/)). +- **Momentic state.** Dashboard run history, AI memory and step caches stay in Momentic. +- **Results.** For standard report files, pass `--reporter junit` or `--reporter json` to `momentic run` or `momentic-mobile run`. Web runs also support `--reporter playwright-json`. +- **AI steps in a Playwright eject.** Momentic says AI actions, AI checks, the step cache, in-flow classification and auto-maintenance have no open-source equivalent. A Playwright port must express each as code, or drop it. +- **Visual baselines.** Momentic `visualDiff` golden files do not move. A KaneAI Visual Comparison step captures a new baseline on its first run. +- **Emulators in KaneAI test runs.** Virtual Mobile configurations are for non-KaneAI test runs only. Use Kane CLI for emulator and simulator runs. + + + +## Related migration guides + +- [How to Migrate Existing Playwright Tests to ](/support/docs/migrate-existing-playwright-tests/): run Playwright scripts through the CDP endpoint. +- [Migration from Katalon](/support/docs/one-click-migration-from-katalon/): import Katalon Studio desktop web test cases into KaneAI New Experience. +- [mabl To KaneAI Migration](/support/docs/mabl-to-kaneai-migration-guide/): re-create mabl tests in KaneAI. +- [testRigor To KaneAI Migration](/support/docs/testrigor-to-kaneai-migration-guide/): re-create testRigor tests in KaneAI. +- [Autosana To KaneAI Migration](/support/docs/autosana-to-kaneai-migration-guide/): re-create Autosana tests in KaneAI. +- [Tester Army To KaneAI Migration](/support/docs/tester-army-to-kaneai-migration-guide/): re-create Tester Army tests in KaneAI. diff --git a/docs/one-click-migration-from-katalon.md b/docs/one-click-migration-from-katalon.md index 95db92ab4..32fd5987a 100644 --- a/docs/one-click-migration-from-katalon.md +++ b/docs/one-click-migration-from-katalon.md @@ -259,6 +259,10 @@ The analysis of your uploaded file determines which cases and steps are supporte No. This flow creates a new Test Manager project. +**Can I import tests from mabl or other tools?** + +No. This importer reads Katalon Studio projects only. For mabl, follow the [mabl to KaneAI migration guide](/support/docs/mabl-to-kaneai-migration-guide/). It shows how to export your tests as code, run them on , and re-create them in KaneAI. + **Will the import modify my Katalon project?** No. The import reads the uploaded archive. It does not synchronize changes back to Katalon. diff --git a/docs/parasoft-to-kaneai-migration-guide.md b/docs/parasoft-to-kaneai-migration-guide.md new file mode 100644 index 000000000..f1e6bf05b --- /dev/null +++ b/docs/parasoft-to-kaneai-migration-guide.md @@ -0,0 +1,382 @@ +--- +id: parasoft-to-kaneai-migration-guide +title: How to migrate from Parasoft to KaneAI +hide_title: true +sidebar_label: Parasoft To KaneAI Migration +description: Plan your Parasoft migration to KaneAI. Run Selenic tests on the TestMu AI Selenium grid, bring test cases into Test Manager, and re-create flows and API calls. +keywords: + - parasoft migration to kaneai + - parasoft to kaneai migration + - migrate from parasoft to kaneai + - how to migrate from parasoft to kaneai + - parasoft selenic selenium grid + - parasoft soatest api tests +url: https://www.testmuai.com/support/docs/parasoft-to-kaneai-migration-guide/ +site_name: TestMu AI +slug: parasoft-to-kaneai-migration-guide/ +canonical: https://www.testmuai.com/support/docs/parasoft-to-kaneai-migration-guide/ +--- + +import CodeBlock from '@theme/CodeBlock'; +import {YOUR_LAMBDATEST_USERNAME, YOUR_LAMBDATEST_ACCESS_KEY} from "@site/src/component/keys"; + +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; +import BrandName, { BRAND_URL } from '@site/src/component/BrandName'; +import { CookieTrackingSignup } from '@site/src/component/CookieTracking'; +import VerifiedTag from '@site/src/component/verifiedTag'; + + + + + + + +# Migrating From Parasoft To KaneAI +* * * +This guide covers your Parasoft migration to KaneAI for Selenic Selenium web UI tests in Java and SOAtest API tests. It does not cover Parasoft Virtualize, Jtest, C/C++test or dotTEST. You run Selenic tests on the Selenium grid, bring test cases into Test Manager, and re-create web flows and API calls in KaneAI. + +Parasoft lists LambdaTest (now ) as a Selenic integration. Its integration page describes Selenic self-healing during test runs in the LambdaTest cloud. + + +[Note: KaneAI does not import or convert Parasoft tests. Selenic tests keep running as Selenium Java code on the grid. You re-create flows in KaneAI in natural language, and rebuild SOAtest REST calls as KaneAI API steps from curl commands.] + + + +*** +## What Moves From Parasoft and Where It Goes + +| Parasoft asset | Where it goes on | How | +|---|---|---| +| Selenic tests (Selenium Java with JUnit, TestNG or Cucumber) | Selenium grid | Change the hub URL and set `LT:Options` | +| Selenic runs on the grid | Test Manager test cases | Automatic linking, or the `tms.tc_id` capability | +| SOAtest structure reports (XML) | Test Manager test cases | AI Test Case Generator | +| SOAtest REST Client requests | API steps in a KaneAI web test | One curl command per request | +| Web flows you maintain going forward | KaneAI web tests | **Automate with KaneAI**, or steps in natural language | +| Selenic recorded data, SOAtest tools and DTP results | Stay in Parasoft | See [What Does Not Carry Over](#what-does-not-carry-over) | + + + +## Before You Start + +- **A account.** Create one on the signup page. Copy your Username and Access Key from Account Settings > [Password & Security](https://www.testmuai.com/login/?redirectTo=https://accounts.lambdatest.com/security/username-accesskey). +- **KaneAI and Test Manager access.** The **Automate with KaneAI** action requires KaneAI access. +- **Selenic.** It supports Selenium 3 (starting with 3.10) and Selenium 4, on Java 11, 17 or 21. You can use its command line after you configure the license. +- **SOAtest.** You save structure reports from the Test Case Explorer. `soatestcli` requires a command line interface license, available with SOAtest Automation Edition. +- **Private apps.** For locally hosted applications, see [ Tunnel](/support/docs/testmu-tunnel/) and [KaneAI tunnel support](/support/docs/kane-ai-geolocation-tunnel-proxy/). + +## Step 1: Collect Your Selenic Tests and SOAtest Files + +### Selenic Tests + +Selenic works on Selenium tests in your own Java project, so there is nothing to export. Tests that Selenic creates from Parasoft Recorder files also live in a Java project. Find where each test class creates its WebDriver, because Step 2 changes that code. + +### SOAtest Files + +SOAtest keeps tests in `.tst` files inside workspace projects. Each `.tst` file can include test suites or scenarios, tools, and inputs. Since version 2024.2, new workspaces save `.tst` files in YAML format by default. + +Save a structure report for each `.tst` file you plan to re-create. Right-click the `.tst` node in the Test Case Explorer and choose **Structure Report > Default Structure Report > Save As XML**. The report lists test suites, test cases, endpoints tested, requirements and data sources. + +### Your Current Commands + +These commands come from Parasoft's docs. In `soatestcli`, the `-resource` option specifies the test suites to run. Check it to see which `.tst` files your pipeline runs. + + + + + + + +```bash +mvn test -DargLine=-javaagent:/path/to/selenic_agent.jar=captureDom=true +``` + + + + +```bash +soatestcli.exe -config "user://Example Configuration" -resource "tests/myTest.tst" +``` + + + + + + +## Step 2: Run Selenic Tests on the Selenium Grid + +Selenic supports parallel test execution in JUnit, TestNG and Cucumber, including environments that use Selenium Grid. On , the driver is a `RemoteWebDriver` pointed at the grid, and your browser and OS choices go in its capabilities. [Migrate Your Selenium Suite](/support/docs/migrate-selenium-test-suite/) walks through the same changes for any Selenium project. + +### Set Your Credentials + +Create a `.env` file in the root of your project with your Username and Access Key. Make sure your tests read these values at runtime: + + + +```text +LT_USERNAME="" +LT_ACCESS_KEY="" +``` + +### Change the Hub URL + +Where your tests create a local driver, create a `RemoteWebDriver` that uses this hub instead: + + + +```text +@hub.lambdatest.com/wd/hub +``` + +Put `https://` and your credentials in front of it: `https://:@hub.lambdatest.com/wd/hub`. + +### Set Your Capabilities + +Set the browser, browser version and platform on your browser options, and your credentials in `LT:Options`. A Selenium 4 example: + + + +```java +SafariOptions browserOptions = new SafariOptions(); +browserOptions.setPlatformName("MacOS Tahoe"); +browserOptions.setBrowserVersion("26"); +HashMap ltOptions = new HashMap(); +ltOptions.put("username", ""); +ltOptions.put("accessKey", ""); +ltOptions.put("w3c", true); +browserOptions.setCapability("LT:Options", ltOptions); +``` + +Build other combinations with the [Capabilities Generator](https://www.testmuai.com/capabilities-generator/). For Selenium 3, see [Selenium Capabilities](/support/docs/selenium-automation-capabilities/). For full JUnit, TestNG and Cucumber projects, see [Selenium With Java](/support/docs/java-with-selenium-running-java-automation-scripts-on-testmu-selenium-grid/) and the [Capability Map](/support/docs/testmu-capability-map/). + +### Keep Selenic in the Run + +To keep Selenic recommendations or self-healing, leave the `-javaagent` argument from Step 1 on your command. Add `selfHealing=true` to the agent options to enable self-healing. Recommendations come from running `selenic_analyzer.jar` after the run. View your test execution results on the Web Automation dashboard. + +## Step 3: Bring Test Cases Into Test Manager + +### Link Selenic Runs + +When a Selenium run on the grid completes, Test Manager creates a ** Automation** project. It holds a test case titled from the run, with BDD Scenarios created from the run's command logs. This automatic linking is supported for Selenium Web frameworks. Use it to track your Selenic runs in Test Manager. + +To link a run to an existing test case instead, add the `tms.tc_id` key, and optionally `project`, to the `LT:Options` map from Step 2. The Test Manager docs spell it `lt:Options`, so do not add a second map. See [Managing Automated Tests with Test Manager](/support/docs/automated-test-cases-with-ai/). + +### Generate Test Cases From SOAtest Reports + +1. In your Test Manager project, open the **Test Case Listing** page and click **Generate With AI**. +2. Click the pin icon, select **Upload from device**, and attach your XML structure reports. The generator accepts JSON or XML files, up to 10 files of 50 MB each. +3. Review the generated test cases, select the ones you want, and click **Create**. + +The generator writes new test cases from your reports. It does not import your SOAtest tests. See [Generate Test Cases with AI](/support/docs/generate-test-cases-with-ai/). + +## 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. The action works on one test case at a time, in the Manual Test Steps or Behaviour Driven Development template. The test case must have steps or scenarios. The docs do not describe this action on test cases created from Selenium runs. See [Create & Manage Test Cases](/support/docs/manual-test-case-creation/#automate-with-kaneai). + +### Start a New Web Test + +On the KaneAI homepage, click **Create a Web Test**. You add steps by typing instructions in natural language, by running slash commands, or by interacting with the application directly. Use your Selenic test steps as a guide. See [Author your First Test](/support/docs/kane-ai-web-test/). + +To record steps as you click and type, use [Manual Interaction](/support/docs/kaneai-manual-interaction/). Verify and assert steps must still be written instructions. + +### Rebuild SOAtest REST Calls as API Steps + +KaneAI API steps live inside a web test. Add an API through the slash command, open the API module, and paste a curl command. KaneAI populates the request details. + +Write one curl command for each SOAtest REST Client you keep, using its URL, method, headers and payload. The REST Client's **Resolved URL** field shows how environment variables in the URL resolve. This POST example comes from [API Testing & Network Assertions](/support/docs/kaneai-kb-api-testing-and-network-assertions/): + +```bash +curl -X POST "https://api.example.com/users" \ + -H "Authorization: Bearer {{secret.api_token}}" \ + -H "Content-Type: application/json" \ + -d '{ + "name": "John Doe", + "email": "john@example.com", + "role": "admin" + }' +``` + +Click **validate** to check the response. A 200 response adds the API to your test steps. A 400 Bad Request or other error is not added automatically, so review it and add it manually if needed. You can paste multiple curl commands at once. KaneAI supports GET, POST, PUT, PATCH and DELETE. The KaneAI docs do not describe the OPTIONS, HEAD, TRACE or custom methods a SOAtest REST Client can send. See [KaneAI API Testing](/support/docs/kane-ai-api-testing/). + +### Reuse Steps and Data + +- **Modules:** Author shared steps, such as a login, once as a [module](/support/docs/kane-ai-modules/). A module groups a sequence of test steps into a single reusable unit. +- **Variables:** Re-create SOAtest environment variables as KaneAI [environment variables](/support/docs/kane-ai-using-variables/). JSON variables are auto-generated from API calls, so later steps can reuse response values. + +### Generate Code + +A test saved as **Ready**, where every step has run and passed, generates code. Selenium Java is "Available on request" in Classic and "Not available" in New Experience. To turn it on, reach out to Support. Selenium Python is "Available (default)" in Classic. Playwright Python and JavaScript are "Available" in New Experience. See [KaneAI Automation Code Generation](/support/docs/kane-ai-automation-code-generation/). + +## Step 5: Run Your KaneAI Tests + +1. In your Test Manager project, go to the **Test Run** section and click **Create Test Run**. Set **Type** to **KaneAI Generated Test Cases**. +2. Add test cases. Only test cases with generated code are available. +3. Assign the test cases and set their configurations. +4. Save the run, click **Run on HyperExecute**, and choose **Run Instances Now** or **Schedule Test Run**. + +See [Execute Test Runs on HyperExecute](/support/docs/kaneai-hyperexecute-test-run-execution/). + +To start a run from CI, copy the Test Run ID from the test run URL. Send it as `test_run_id` in a POST request to `https://test-manager-api.lambdatest.com/api/atm/v1/hyperexecute`, with Basic Authentication using your username and access key. See [Test Automation with CI/CD](/support/docs/kaneai-ci-cd-automation/). + +[Configurations in KaneAI & Test Manager](/support/docs/test-runs-configurations/) describes the device scope. With the KaneAI toggle on, the available platforms are Desktop and Real Device. The doc also states: + +- "Native app testing on Real Devices is available only for KaneAI-generated test runs." +- "Mobile browser testing on Real Devices is available for non-KaneAI test runs only." +- "Virtual Mobile configurations are available for non-KaneAI test runs only." + +## What Does Not Carry Over + +- **Selenic recorded data.** Selenic saves test execution data to `/parasoft/recorded_data` and builds recommendations from it. That data stays with Selenic, and KaneAI tests do not use it. +- **SOAtest tools and data sources.** Tools in your `.tst` files, such as the JSON Assertor and JSON Data Bank, stay in SOAtest. So do suite, project and global data sources. Re-create the checks you need as KaneAI steps. +- **Results and history.** Results that Selenic or `soatestcli` published to Parasoft DTP stay in DTP. + + + +## Related migration guides + +- [Migrate Your Selenium Suite](/support/docs/migrate-selenium-test-suite/): run an existing Selenium suite on the cloud grid. +- [ Capability Map](/support/docs/testmu-capability-map/): capability mapping for moves from BrowserStack and Sauce Labs. +- [Sauce Labs To KaneAI Migration](/support/docs/saucelabs-to-kaneai-migration-guide/): move from Sauce Labs to KaneAI. +- [BrowserStack To KaneAI Migration](/support/docs/browserstack-to-kaneai-migration-guide/): move from BrowserStack to KaneAI. diff --git a/docs/saucelabs-to-kaneai-migration-guide.md b/docs/saucelabs-to-kaneai-migration-guide.md new file mode 100644 index 000000000..cf8a5adb2 --- /dev/null +++ b/docs/saucelabs-to-kaneai-migration-guide.md @@ -0,0 +1,356 @@ +--- +id: saucelabs-to-kaneai-migration-guide +title: How to migrate from Sauce Labs to KaneAI +hide_title: true +sidebar_label: Sauce Labs To KaneAI Migration +description: Plan your Sauce Labs migration to KaneAI. Run Selenium, Appium and saucectl scripts on TestMu AI, bring test cases into Test Manager, and re-create flows. +keywords: + - sauce labs migration to kaneai + - sauce labs to kaneai migration + - migrate from sauce labs to kaneai + - how to migrate from sauce labs to kaneai + - sauce ai test authoring to kaneai + - saucectl to testmu ai migration + - saucectl +url: https://www.testmuai.com/support/docs/saucelabs-to-kaneai-migration-guide/ +site_name: TestMu AI +slug: saucelabs-to-kaneai-migration-guide/ +canonical: https://www.testmuai.com/support/docs/saucelabs-to-kaneai-migration-guide/ +--- + +import CodeBlock from '@theme/CodeBlock'; +import {YOUR_LAMBDATEST_USERNAME, YOUR_LAMBDATEST_ACCESS_KEY} from "@site/src/component/keys"; + +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; +import BrandName, { BRAND_URL } from '@site/src/component/BrandName'; +import { CookieTrackingSignup } from '@site/src/component/CookieTracking'; +import VerifiedTag from '@site/src/component/verifiedTag'; + + + + + +# Migrating From Sauce Labs To KaneAI +* * * +This guide covers your Sauce Labs migration to KaneAI and shows you how to move your testing to . KaneAI is the testing agent that turns natural language into end-to-end tests for web and mobile apps. The steps cover scripts, app builds, test cases and Sauce AI for Test Authoring tests. + +[Note: KaneAI does not import or convert Sauce Labs tests. You run your scripts on the cloud, bring test cases into Test Manager, and re-create flows in KaneAI in natural language.] + +*** +## What Moves From Sauce Labs and Where It Goes + +| Sauce Labs asset | Where it goes on | How | +|---|---|---| +| Selenium scripts | Selenium grid or HyperExecute | [Sauce Labs to guide](/support/docs/saucelabs-to-testmu-migration-guide/) or [Sauce Labs to HyperExecute](/support/docs/saucelabs-to-hyperexecute-migrate/) | +| Appium scripts | Appium grid | [Migrate Appium Tests From Sauce Labs](/support/docs/migrate-appium-tests-from-sauce-labs/) | +| Cypress, Playwright, TestCafe, Espresso and XCUITest suites run with saucectl | cloud | Framework guides for [Cypress](/support/docs/getting-started-with-cypress-testing/), [Playwright](/support/docs/playwright-test-runner/), [TestCafe](/support/docs/npm-plugin-for-testcafe-integration-with-testmu/), [Espresso](/support/docs/getting-started-with-espresso-testing/) and [XCUITest](/support/docs/getting-started-with-xcuitest/) | +| Sauce AI for Test Authoring test cases | cloud for generated code, and KaneAI | Export the code (Step 1), run it (Step 2) and re-create the test (Step 4) | +| Sauce AI Data Variables | KaneAI variables and secrets | Re-create them (Step 4) | +| Chrome DevTools recordings replayed with saucectl | KaneAI | Perform the flow again in KaneAI (Step 4) | +| App builds in Sauce Labs App Storage | KaneAI app tests and Appium tests | Download them (Step 1), then upload in a [KaneAI app test](/support/docs/kane-ai-app-test/), or [through the API](/support/docs/application-setup-via-api/) for Appium tests | +| Test cases created in TestRail from Sauce Labs results | Test Manager | One-click [TestRail importer](/support/docs/one-click-migration-from-testrail/) (Step 3) | +| Sauce Connect tunnels | Tunnel | A [ Tunnel](/support/docs/kane-ai-geolocation-tunnel-proxy/#tunnel-support), selected in KaneAI (Step 5) | + +## Before You Start + +- **A account.** Create one on the signup page. Copy your Username and Access Key from Account Settings > [Password & Security](https://www.testmuai.com/login/?redirectTo=https://accounts.lambdatest.com/security/username-accesskey). +- **KaneAI and Test Manager access.** **Automate with KaneAI** and **Create and Automate** require KaneAI access. You create KaneAI test runs in Test Manager. +- **Support requests, if needed.** Reach out to Support to enable New Experience, or code export frameworks marked as available on request. +- **saucectl.** It reads `SAUCE_USERNAME` and `SAUCE_ACCESS_KEY` from environment variables or a `credentials.yml` file. The npm install requires Node.js 16 or higher and npm 8 or higher. +- **Sauce AI for Test Authoring, if you use it.** It is a paid add-on for Sauce Labs Enterprise accounts. + +## Step 1: Collect What You Need From Sauce Labs + +Sauce Labs keeps test assets, including videos, screenshots and logs, for 30 days. Test parameters and metadata remain available. Download what you need first. + +List your jobs, then download the artifacts you want to keep. The list shows 20 jobs per page by default, so add `--page` or `--size` to see more: + + + +```bash +saucectl jobs list --out json +saucectl artifacts download --target-dir my-artifacts-dir +``` + + +The default region is `us-west-1`. Add `--region eu-central-1` for the EU Central data center. + +Mobile App Storage keeps uploaded apps for up to 60 days. List your builds, then download the ones you need: + + + +```bash +saucectl storage list --out json +saucectl storage download 0244d466-ff99-4fa2-bee0-64afb2c407b0 --filename app.apk +``` + + +Replace the sample file ID and file name with values from the list. + +If you use Sauce AI for Test Authoring, save two things from each test case: + +1. **The script.** Open **Test Authoring** > **Test Cases and Suites** and select the test case. On the **Code** tab, pick a language and framework in **Choose language**, then click **Get Code**. Copy the script into your project. +2. **The intent.** The test case workspace shows the original prompts and the intent of each step. Keep them for Step 4. + +Code options include Selenium, Playwright, WebdriverIO, Appium, Espresso and XCUITest, by language and platform. The script reflects the current version of the test case, so regenerate it after any edit. + +## Step 2: Run Your Existing Scripts on + +Your Selenium and Appium scripts keep their test logic. You change the credentials, the endpoint and the capabilities: + + + + + + + +```text +https://ondemand.us-west-1.saucelabs.com/wd/hub +``` + + + + +```text +@hub.lambdatest.com/wd/hub +``` + + + + +```text +@mobile-hub.lambdatest.com/wd/hub +``` + + + + +The Sauce Labs endpoint above is for the US West data center. For , put `https://YOUR_USERNAME:YOUR_ACCESS_KEY` before the grid URL. + +Follow the [Sauce Labs to migration guide](/support/docs/saucelabs-to-testmu-migration-guide/) for Selenium and [Migrate Appium Tests From Sauce Labs](/support/docs/migrate-appium-tests-from-sauce-labs/) for Appium. Map `sauce:options` to `LT:Options` with the [capability map](/support/docs/testmu-capability-map/) and the [Capabilities Generator](https://www.testmuai.com/capabilities-generator/). + +saucectl runs tests in the Sauce Labs cloud, so its `config.yml` stays behind. Use each framework's guide instead. For example, the Cypress CLI reads capabilities from `lambdatest-config.json`. + +Treat code generated by Sauce AI like your other scripts in that framework. Replace any Sauce Labs endpoint, credentials or capabilities it contains. + +## Step 3: Bring Test Cases Into Test Manager + +**Automate with KaneAI** starts from a saved test case in Test Manager. Bring your test cases in first: + +- **TestRail, qTest, Xray or Zephyr Scale.** Use the one-click importers for [TestRail](/support/docs/one-click-migration-from-testrail/), [qTest](/support/docs/one-click-migration-from-qtest/), [Xray](/support/docs/one-click-migration-from-xray/) (Jira Cloud) or [Zephyr Scale](/support/docs/one-click-migration-from-zephyr-scale/) (Jira Cloud). Sauce Labs documents a TestRail integration in which the TestRail CLI creates test cases from saucectl JUnit reports. +- **Spreadsheets.** Use [CSV import](/support/docs/csv-import/). Map at least one column to **Title**. Each file can be up to 10 MB. +- **Requirements.** The [AI Test Case Generator](/support/docs/generate-test-cases-with-ai/) writes test cases from text and files, including your saved Sauce AI prompts. + +If you keep running scripts on , Test Manager can also track those runs: + +- **Automatic linking.** Test Manager can create test cases from completed runs in an automatically created ** Automation** project. Their BDD scenarios are generated from each run's command logs. This works for Selenium Web frameworks only. See [automatic linking](/support/docs/automated-test-cases-with-ai/#automatic-linking). +- **Capability linking.** Add the `tms.tc_id` key to `lt:Options` to link a run to a test case, on HyperExecute and Web Automation tests. See [capability linking](/support/docs/automated-test-cases-linked-using-capability/). + +## Step 4: Re-create Your Flows in KaneAI + +In a KaneAI session, you add steps in natural language, with slash commands or by interacting with your app. Start from what you have: + +- **A test case in Test Manager.** Open it and click **Automate with KaneAI** in its **Automate** section. KaneAI opens a session pre-filled with the steps, where you author and run the test. The action works on one test case at a time. It works with the Manual Test Steps and Behaviour Driven Development templates, and the test case must have steps or scenarios. See [Automate with KaneAI](/support/docs/manual-test-case-creation/#automate-with-kaneai). +- **Generated test cases.** In the AI Test Case Generator, **Create and Automate** saves the selected test cases and sends them to KaneAI. It is experimental, so review the authored steps. +- **A Sauce AI test case.** Create a [KaneAI web test](/support/docs/kane-ai-web-test/) or [app test](/support/docs/kane-ai-app-test/). Write the objective in natural language from the prompts and step intents you saved. +- **A recorded or manual flow.** [Manual Interaction](/support/docs/kaneai-manual-interaction/) records the clicks, typing and navigation you perform in a KaneAI session as steps. It works on desktop web, Android apps and iOS apps in portrait, not mobile browsers. Write checks as instructions, because interactions cannot record assertions. + +Then reuse what you can: + +- Group repeated steps into [modules](/support/docs/kane-ai-modules/). +- Re-create Data Variables as [KaneAI variables](/support/docs/kane-ai-using-variables/), and passwords or tokens as [secrets](/support/docs/kane-ai-secrets/). +- Replace Sauce Visual checks with a [Visual Comparison step](/support/docs/kaneai-smartui-visual-testing/). Its first run captures a new baseline. + +A test saved as **Ready**, with every step run and passed, generates code. The [code generation](/support/docs/kane-ai-automation-code-generation/) frameworks depend on the authoring experience: + +- **Classic:** Selenium Python and Appium Python by default. Selenium Java and Playwright Python, C# and JavaScript on request. +- **New Experience:** Playwright Python and Playwright JavaScript. Appium Python is coming soon. + +## Step 5: Run Your KaneAI Tests + +Run KaneAI tests in a Test Manager test run on HyperExecute: + +1. In your project, open **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 and give it at least one configuration. Click **Save test run**. +4. Click **Run on HyperExecute** and choose **Run Instances Now** or **Schedule Test Run**. + +See [Execute Test Runs on HyperExecute](/support/docs/kaneai-hyperexecute-test-run-execution/). Replace Sauce AI schedules with **Schedule Test Run** or your CI pipeline. + +With the **KaneAI** toggle ON, configurations offer the Desktop and Real Device platforms. Native app testing on Real Devices is available only for KaneAI-generated test runs. Mobile browser testing on real devices and Virtual Mobile configurations are available for non-KaneAI test runs only. See [Configurations in KaneAI & Test Manager](/support/docs/test-runs-configurations/). + +From CI, copy the Test Run ID from the test run URL and send it in a POST request to `https://test-manager-api.lambdatest.com/api/atm/v1/hyperexecute`. Use your username and access key for Basic Authentication. See [Test Automation with CI/CD](/support/docs/kaneai-ci-cd-automation/). + +For a KaneAI web test on a site behind a firewall, start a tunnel with `--env ht-prod` and select it under **Advanced Settings**: + + + +
+ +{`./LT --user ${YOUR_LAMBDATEST_USERNAME()} --key ${YOUR_LAMBDATEST_ACCESS_KEY()} --env ht-prod -v -n TUNNEL_NAME`} + +
+ +In CI, pass the tunnel name in the `tunnel` field. See [KaneAI tunnel support](/support/docs/kane-ai-geolocation-tunnel-proxy/). + +## What Does Not Carry Over + +- **Run history.** No importer reads Sauce Labs job history, so your runs start a new history. Sauce Labs purges job asset files after 30 days. +- **Sauce AI test cases, suites and schedules.** KaneAI does not import them. You re-create them. +- **Hidden Data Variables.** Their values cannot be viewed after they are created. Take them from your own records. +- **saucectl files, recordings and tunnels.** KaneAI does not import saucectl `config.yml` files, Chrome DevTools recordings or Sauce Connect settings. See the table above. +- **Sauce Visual baselines.** A baseline is what a snapshot is compared to. KaneAI captures a new baseline on the first run of each Visual Comparison step. +- **Cypress and WebdriverIO code export.** KaneAI does not generate Cypress or WebdriverIO code. Keep those suites as scripts on the cloud. +- **Other products.** This guide does not cover Sauce Labs Error Reporting or Mobile App Distribution. + + + +## Related migration guides + +- [Sauce Labs To Migration](/support/docs/saucelabs-to-testmu-migration-guide/): Selenium 4 and Selenium 3 scripts. +- [Migrate Appium Tests From Sauce Labs](/support/docs/migrate-appium-tests-from-sauce-labs/): Appium mobile test suites. +- [Sauce Labs to HyperExecute](/support/docs/saucelabs-to-hyperexecute-migrate/): Selenium suites on HyperExecute. +- [ Capability Map](/support/docs/testmu-capability-map/): capability mapping for Sauce Labs users. +- [BrowserStack To KaneAI Migration](/support/docs/browserstack-to-kaneai-migration-guide/): the same path for BrowserStack users. +- [Parasoft To KaneAI Migration](/support/docs/parasoft-to-kaneai-migration-guide/): move from Parasoft Selenic and SOAtest to KaneAI. diff --git a/docs/saucelabs-to-lambdatest-migration-guide.md b/docs/saucelabs-to-lambdatest-migration-guide.md index 8d99202f3..8cb01a481 100644 --- a/docs/saucelabs-to-lambdatest-migration-guide.md +++ b/docs/saucelabs-to-lambdatest-migration-guide.md @@ -549,3 +549,4 @@ Visit Web Automation dashboard to view your test execution result. ## Related migration guides - [Migrate Appium Tests from Sauce Labs](/support/docs/migrate-appium-tests-from-sauce-labs/) — move your Appium mobile test suite from Sauce Labs to TestMu AI. +- [Sauce Labs to KaneAI migration guide](/support/docs/saucelabs-to-kaneai-migration-guide/): bring test cases into Test Manager and re-create Sauce AI tests in KaneAI. diff --git a/docs/tester-army-to-kaneai-migration-guide.md b/docs/tester-army-to-kaneai-migration-guide.md new file mode 100644 index 000000000..3fa3867d1 --- /dev/null +++ b/docs/tester-army-to-kaneai-migration-guide.md @@ -0,0 +1,411 @@ +--- +id: tester-army-to-kaneai-migration-guide +title: How to migrate from Tester Army to KaneAI +hide_title: true +sidebar_label: Tester Army To KaneAI Migration +description: Plan your Tester Army migration to KaneAI. Retrieve test steps with the Tester Army CLI or API, import them into Test Manager, and re-create them in KaneAI. +keywords: + - tester army migration to kaneai + - tester army to kaneai migration + - migrate from tester army to kaneai + - how to migrate from tester army to kaneai + - testerarmy to kaneai + - export tester army tests +url: https://www.testmuai.com/support/docs/tester-army-to-kaneai-migration-guide/ +site_name: TestMu AI +slug: tester-army-to-kaneai-migration-guide/ +canonical: https://www.testmuai.com/support/docs/tester-army-to-kaneai-migration-guide/ +--- + +import CodeBlock from '@theme/CodeBlock'; +import {YOUR_LAMBDATEST_USERNAME, YOUR_LAMBDATEST_ACCESS_KEY} from "@site/src/component/keys"; + +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; +import BrandName, { BRAND_URL } from '@site/src/component/BrandName'; +import { CookieTrackingSignup } from '@site/src/component/CookieTracking'; +import VerifiedTag from '@site/src/component/verifiedTag'; + + + + + + + +# Migrating From Tester Army To KaneAI +* * * +This guide covers your Tester Army migration to KaneAI: retrieving tests, importing them into Test Manager, and re-creating them in KaneAI or Kane CLI. Tester Army (written TesterArmy in its own docs) uses AI agents to run natural language test steps on web and mobile apps. + + +[Note: KaneAI does not import or convert Tester Army tests. You retrieve each test's steps with the Tester Army CLI or API and import them into Test Manager through a CSV file. Then you re-create each test in natural language.] + + + +*** +## What Moves From Tester Army and Where It Goes + +| Tester Army asset | Where it goes on | How | +|---|---|---| +| Saved web and mobile tests | KaneAI tests or Kane CLI `_test.md` files | Re-create from the steps | +| Test titles and steps | Test Manager test cases | Import a CSV that you build | +| `login` steps and test accounts | KaneAI secrets and TOTP variables | Enter the values again | +| Preparation Test | A KaneAI module | Author the login once | +| `files` steps | KaneAI Files | Upload each file again | +| Groups | Test Manager test runs | Add the test cases | +| Production Monitoring | Scheduled test runs | Schedule the test run | +| Group webhooks | The KaneAI test run API | Call it from your pipeline | +| Run history and Issues | Stay in Tester Army | Not part of a test | + + + +## Before You Start + +- **A account with KaneAI access.** The **Automate with KaneAI** action requires it. Create one on the signup page. Copy your username and access key from Account Settings > [Password & Security](https://www.testmuai.com/login/?redirectTo=https://accounts.lambdatest.com/security/username-accesskey). +- **The Tester Army CLI or an API key.** Step 1 covers the CLI. Create API keys under **Settings > API Keys** in Tester Army. Tester Army lists the CLI and the API in every plan, including Free. +- **Your test account details.** Tester Army's API returns each saved credential's label and username, but not its password or authenticator secret. +- **A device build for KaneAI app tests.** Tester Army uses simulator and emulator builds, "not an `.ipa` built for physical devices". KaneAI app tests run on real devices, so upload an APK for Android or an IPA for iOS. +- **Kane CLI, if you want tests as files.** It needs Google Chrome, and Node.js 18 or higher for npm. See [Installing Kane CLI](/support/docs/kane-cli-installation/). + +## Step 1: Retrieve Your Tester Army Tests + +A Tester Army test describes one user flow as 1 to 30 ordered steps. The `ta tests get` command returns one test with its steps, and `ta tests list` lists a project's tests. Add `--json` for machine-readable output. With the API, pass the returned `nextCursor` as `cursor` to get the next page. + + + + + +```bash +npm install -g testerarmy +ta auth +ta projects list --json +ta tests list --project --all --json +ta tests get --json +``` + + + + +```bash +# One test with its steps +curl https://tester.army/api/v1/tests/ \ + -H "Authorization: Bearer $TESTERARMY_API_KEY" + +# Tests in a project, up to 100 per page +curl "https://tester.army/api/v1/tests?projectId=&limit=100" \ + -H "Authorization: Bearer $TESTERARMY_API_KEY" +``` + + + + + + +Each test has a `title`, a `platform` of `web` or `mobile`, and a `steps` list. Each step has a `type`: `act`, `assert`, `login`, `files`, `screenshot`, `javascript` or `microphone`. The `act`, `assert`, `login` and `files` steps carry their text in a `title`. Every run skips a step marked `disabled: true`. + +Tests saved in Tester Army are natural language steps, not framework scripts. They have no exported code to run on the cloud grid. This guide does not cover Tester Army's separate open source e2e framework. To run e2e web tests on cloud Chrome, see [e2e by TesterArmy](https://www.testmuai.com/blog/e2e-by-testerarmy/). + +## Step 2: Import Tests Into Test Manager + +Test Manager has no importer for Tester Army tests, but it imports test cases from CSV. Build a CSV with one test per row. Put the test `title` in one column and the step titles, numbered `1. ... 2. ...`, in another. + + + + + +```json +{ + "title": "Billing plan check", + "steps": [ + { "title": "Log in with the saved admin account.", "type": "login" }, + { "title": "Open the billing settings page.", "type": "act" }, + { "title": "Verify the billing page shows the current plan.", "type": "assert" } + ] +} +``` + + + + +```csv +Title,Steps +Billing plan check,"1. Log in with the saved admin account. 2. Open the billing settings page. 3. Verify the billing page shows the current plan." +``` + + + + +Then import the file: + +1. In your Test Manager project, go to **Add Test Case > Import CSV**. +2. Upload the file and select the **Test cases use a single row** layout. +3. Map your columns to **Title** and **Steps**. Mapping at least one CSV header to **Title** is mandatory. +4. Map the values, review the preview, and start the import. + +Each file can be up to 10 MB. See [Import Test Cases from CSV](/support/docs/csv-import/). + +Alternatively, attach the JSON in the [AI Test Case Generator](/support/docs/generate-test-cases-with-ai/) through **Generate With AI**. It writes new test cases from the file instead of importing your tests. + +## Step 3: Re-create Your Tests in KaneAI + +### Start From a Test Case + +Open an imported test case and click **Automate with KaneAI** in its **Automate** section. A KaneAI session opens with the test case's steps pre-filled, where you author the test and then execute it. This works on one saved test case at a time, and the test case must have steps. See [Create & Manage Test Cases](/support/docs/manual-test-case-creation/#automate-with-kaneai). + +### Start a New Test + +On the KaneAI homepage, click **Create a Web Test**, or **Create an App Test** for a mobile app. Then write each step in natural language. See [Author your First Test](/support/docs/kane-ai-web-test/) and [App Test](/support/docs/kane-ai-app-test/). + +### Rewrite Each Step Type + +- **`act` and `assert`:** Write actions as instructions and checks as natural language assertions, such as `assert "Your order has been placed" is displayed`. See [Assertions & Validation](/support/docs/kaneai-kb-assertions-and-validation/). +- **`login`:** Store passwords as [secrets](/support/docs/kane-ai-secrets/) and reference them with double curly braces. For authenticator codes, create a [TOTP variable](/support/docs/kaneai-totp/) from the Base32 key that Tester Army calls the authenticator secret. +- **`files`:** In a web test, add the file under **KaneAI > Variables > Files** and reference it as `{{file.alias}}`. In an app test, upload the file to the session, and KaneAI injects it into the device's storage. See [Upload and Download Files](/support/docs/kaneai-upload-and-download-files/). +- **`screenshot`:** A [test run instance](/support/docs/kaneai-test-run-instance-view/) shows a screenshot for each executed step. For baseline comparisons, add a [Visual Comparison](/support/docs/kaneai-smartui-visual-testing/) step. +- **`javascript`:** In a web test, type `/`, choose JavaScript, and paste the code. Tester Army fails this step when the code throws or returns `{ success: false, reason }`. KaneAI stores a returned value in a variable, so add assertions for those checks. See [JavaScript Execution](/support/docs/kane-ai-javascript-execution/). + +### Reuse Login Steps + +A Tester Army Preparation Test logs in once and shares that session with the tests in a group. In KaneAI, save the login steps as a [module](/support/docs/kane-ai-modules/). Add it to other tests by typing `/` and selecting **Add Module**. + +### Generate Code + +A test saved as **Ready**, where every step has run and passed, generates code. In New Experience, which is being rolled out in phases, web tests generate Playwright Python or JavaScript. In Classic, Selenium Python is the default, and Selenium Java and Playwright are available on request. App tests generate Appium Python in Classic, which is "Coming soon" in New Experience. See [KaneAI Automation Code Generation](/support/docs/kane-ai-automation-code-generation/). + +### Re-create Tests as Kane CLI Files + +Kane CLI runs natural language Markdown tests from `_test.md` files in your repository. Each `##` heading marks a step, and the agent reads the body under it. A step body should end in a check, so merge each `act` step with the `assert` step after it: + +```markdown +--- +mode: testing +url: https://app.example.com +--- + +# Billing plan check + +## Log in +Log in with {{admin_email}} and {{admin_password}}. Verify the dashboard loads. + +## Check the current plan +Open the billing settings page. Verify the billing page shows the current plan. +``` + +Save the file as `billing_test.md`. Then install Kane CLI, sign in, and run the test: + +```bash +npm install -g @testmuai/kane-cli +kane-cli login --oauth +kane-cli testmd run billing_test.md --variables-file ./vars.json +``` + +The variables file supplies `{{admin_email}}` and `{{admin_password}}`. Set `"secret": true` on the password to mask it in logs. See [Variables & Context](/support/docs/kane-cli-variables-and-context/). The first run authors each step and saves a recording, and later runs replay from the cache. See [Test.md](/support/docs/kane-cli-testmd/). + +- **Code export:** Add `--code-export --code-language python` or `javascript` to generate Playwright code. It requires a successful upload to Test Manager. See [Running test.md files](/support/docs/kane-cli-testmd-running/#code-export). +- **Shared login and guidance:** Move the login into a helper file that you add with `@import ./helpers/login.md`. Copy project memory and agent instructions into a context file such as `.testmuai/context.md`. +- **Mobile apps:** Kane CLI runs mobile tests on virtual devices only, the iOS Simulator and the Android Emulator. Local mobile runs need macOS on Apple Silicon. See [Mobile Testing with Kane CLI](/support/docs/kane-cli-mobile/). + +## Step 4: Run Your Tests + +### KaneAI Test Runs + +A Tester Army group of tests maps to a Test Manager test run. + +1. In your project, open **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 the test cases and set their configurations. +4. Save the run, click **Run on HyperExecute**, and choose **Run Instances Now** or **Schedule Test Run**. + +See [Execute Test Runs on HyperExecute](/support/docs/kaneai-hyperexecute-test-run-execution/). + +[Configurations in KaneAI & Test Manager](/support/docs/test-runs-configurations/) sets the scope. With the KaneAI toggle on, the platforms are Desktop and Real Device. The doc also states: + +- "Native app testing on Real Devices is available only for KaneAI-generated test runs." +- "Mobile browser testing on Real Devices is available for non-KaneAI test runs only." +- "Virtual Mobile configurations are available for non-KaneAI test runs only." + +So in KaneAI test runs, you run your Tester Army simulator and emulator coverage on real devices. + +Other Tester Army triggers and environments: + +- **Production Monitoring:** Click the three dots next to a test run and select **Create Schedule**. See [Scheduled Test Runs](/support/docs/kaneai-scheduled-test-runs/). +- **Group webhooks:** POST the test run ID from its URL to `https://test-manager-api.lambdatest.com/api/atm/v1/hyperexecute`. Use Basic Authentication with your username and access key. See [Test Automation with CI/CD](/support/docs/kaneai-ci-cd-automation/). +- **Environments:** For web tests, fill **Replace Test Execution URL** when you run on HyperExecute. See [Dynamic URL Replacement](/support/docs/kaneai-dynamic-url-replacement/). + +### Kane CLI Suites on the Cloud Grid + +The `kane-cli testrun run --remote` command sends a suite of `_test.md` files to HyperExecute. Web suites run on Chrome, and mobile suites run on a virtual emulator or simulator. Your plan must include HyperExecute with macOS runner concurrency. + + + +```bash +kane-cli plugin install remote-execution +kane-cli testrun run tests/web/ --remote --parallel 4 --on-failure fail-fast +``` + +See [Remote runs on the cloud grid](/support/docs/kane-cli-remote-execution/). + +## What Does Not Carry Over + +- **Run history and Issues.** Verdicts, videos, transcripts, logs and the deduplicated Issues list stay in Tester Army. It exports group runs as JUnit XML. +- **Email inboxes and phone numbers.** Tester Army supplies these for verification codes. Plan another way to receive those codes. +- **Exploration agent and discovery runs.** They have no saved steps to copy. +- **`microphone` steps.** KaneAI has no documented microphone step. Its [Chrome Options](/support/docs/kaneai-chrome-options/) for web tests list `--use-file-for-fake-audio-capture` as an example switch. +- **Mobile viewports.** Tester Army can run web tests at a 390 x 844 `mobile` viewport. With the KaneAI toggle on, mobile browser testing is not available. + + + +## Related migration guides + +- [Import Test Cases from CSV](/support/docs/csv-import/): CSV import in Test Manager. +- [Migration from Katalon](/support/docs/one-click-migration-from-katalon/): Katalon Studio web tests into KaneAI. +- [Autosana To KaneAI Migration](/support/docs/autosana-to-kaneai-migration-guide/): from Autosana flows. +- [Momentic To KaneAI Migration](/support/docs/momentic-to-kaneai-migration-guide/): from Momentic tests. +- [mabl To KaneAI Migration](/support/docs/mabl-to-kaneai-migration-guide/): from mabl tests. +- [testRigor To KaneAI Migration](/support/docs/testrigor-to-kaneai-migration-guide/): from testRigor tests. diff --git a/docs/testim-integration.md b/docs/testim-integration.md index 8a5f73e95..fa3b45573 100644 --- a/docs/testim-integration.md +++ b/docs/testim-integration.md @@ -129,6 +129,8 @@ Testim provides an automated testing platform to create stable tests using AI Na Integrating with Testim lets you run Testim automated tests on cloud-based grid across 3000+ real browsers and OS. +If you plan to move off Testim, the [Testim to KaneAI migration guide](/support/docs/testim-to-kaneai-migration-guide/) shows what Testim can export and how to re-create tests in KaneAI. + ## Prerequisites - Create an account on Testim. - Create a account. You can [sign up for free](https://www.testmuai.com/register/?redirectTo=https://accounts.lambdatest.com/dashboard). diff --git a/docs/testim-to-kaneai-migration-guide.md b/docs/testim-to-kaneai-migration-guide.md new file mode 100644 index 000000000..4d7a72f1c --- /dev/null +++ b/docs/testim-to-kaneai-migration-guide.md @@ -0,0 +1,338 @@ +--- +id: testim-to-kaneai-migration-guide +title: How to migrate from Testim to KaneAI +hide_title: true +sidebar_label: Testim To KaneAI Migration +description: Plan your Testim migration to KaneAI. Export Testim tests as Playwright code, run them on TestMu AI, bring test cases into Test Manager and re-create flows. +keywords: + - testim migration to kaneai + - testim to kaneai migration + - migrate from testim to kaneai + - how to migrate from testim to kaneai + - testim playwright export + - testim cli +url: https://www.testmuai.com/support/docs/testim-to-kaneai-migration-guide/ +site_name: TestMu AI +slug: testim-to-kaneai-migration-guide/ +canonical: https://www.testmuai.com/support/docs/testim-to-kaneai-migration-guide/ +--- + +import CodeBlock from '@theme/CodeBlock'; +import {YOUR_LAMBDATEST_USERNAME, YOUR_LAMBDATEST_ACCESS_KEY} from "@site/src/component/keys"; + +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; +import BrandName, { BRAND_URL } from '@site/src/component/BrandName'; +import { CookieTrackingSignup } from '@site/src/component/CookieTracking'; +import VerifiedTag from '@site/src/component/verifiedTag'; + + + + + +# Migrating From Testim To KaneAI +* * * +This guide covers your Testim migration to KaneAI: what Testim can export, where it goes on , and how to re-create and run tests. + +[Note: KaneAI does not import or convert Testim tests. You export what Testim's docs say it can export and run the exported Playwright code on . You then bring test cases into Test Manager and re-create each flow in KaneAI in natural language.] + +*** +## What Moves From Testim and Where It Goes + +| Testim asset | Where it goes on | How | +|---|---|---| +| Web tests exported as Playwright code | cloud grid | Export each test, then connect it to the CDP endpoint (Steps 1 and 2) | +| Web tests you keep running in Testim for now | Selenium grid | Testim CLI with the `--grid` flag (Step 2) | +| Test steps in PDF run reports | Test Manager test cases | The AI Test Case Generator writes new test cases from the reports (Step 3) | +| TestRail, qTest or Xray test cases linked to Testim tests | Test Manager test cases | One-click importer for that tool (Step 3) | +| CSV export from the Test List view | Test Manager test cases | CSV import, if the file lists tests rather than runs (Step 3) | +| Web and mobile app test flows | KaneAI web and app tests | Automate with KaneAI, or author in natural language (Step 4) | +| Groups, shared steps, test data, custom code, visual and API steps | KaneAI modules, parameters, datasets, JavaScript, Visual Comparison and API steps | Re-create them in KaneAI (Step 4) | +| Run history and results | Stays in Testim | Export to CSV or PDF for your records | + + + + + + + + +## Before You Start + +- **A account.** Create one on the signup page. Copy your Username and Access Key from Account Settings > [Password & Security](https://www.testmuai.com/login/?redirectTo=https://accounts.lambdatest.com/security/username-accesskey). +- **KaneAI access.** **Automate with KaneAI** and **Create and Automate** both require it. +- **A Testim professional plan.** You need it for the code export, the CSV export, third-party grids or the test management integrations. Testim marks each of these as a pro feature. +- **Node.js.** You need it only if you run the Testim CLI. + +## Step 1: Export Your Tests From Testim + +Three Testim exports can help with this move. KaneAI imports none of them as tests. + +**Playwright code.** Testim can export the test that is open in its Editor as code adapted for Playwright. Add this suffix to the end of the URL in your browser, then press Enter. + + + +```text +?embedMode=true&exportPuppeteer=true&exportSelenium=true&exportPlaywright=true +``` + +The test's code opens in a code viewer. Select the **Playwright** tab, then click **Copy code**. Testim notes that the code may need manual adjustments, as its code comments instruct, and that some steps may not be supported. + +**PDF run reports.** After a run, open the three-dot menu on the test screen and select **Generate PDF run report**. Choose a screenshot option, then click **Generate** to download the report. The report lists the test steps and their results. + +**Test List CSV.** On the professional plan, go to **Test List > Tests** and click **Export to CSV**. Testim's doc calls this file a CSV of the execution runs and does not list its columns. Check the columns before you import the file. + +## Step 2: Run Exported Playwright Code on + +Save the copied code in a Playwright project and make the changes its comments call for. Testim's doc does not name the language or test runner of the export, so check the code first. + +Set your credentials as environment variables. On Linux or macOS: + + + +
+ +{`export LT_USERNAME="${ YOUR_LAMBDATEST_USERNAME()}" +export LT_ACCESS_KEY="${ YOUR_LAMBDATEST_ACCESS_KEY()}"`} + +
+ +If the script launches a local browser, replace that launch call with a connection to the CDP endpoint. The `capabilities` object selects the browser and OS for the run. In JavaScript, the connection looks like this: + + + +```javascript +const { chromium } = require('playwright') +const { expect } = require('@playwright/test'); + +(async () => { + const capabilities = { + 'browserName': 'Chrome', // Browsers allowed: `Chrome`, `MicrosoftEdge`, `pw-chromium`, `pw-firefox` and `pw-webkit` + 'browserVersion': 'latest', + 'LT:Options': { + 'platform': 'Windows 10', + 'build': 'Playwright Sample Build', + 'name': 'Playwright Sample Test', + 'user': process.env.LT_USERNAME, + 'accessKey': process.env.LT_ACCESS_KEY, + } + } + + const browser = await chromium.connect({ + wsEndpoint: `wss://cdp.lambdatest.com/playwright?capabilities=${encodeURIComponent(JSON.stringify(capabilities))}` + }) + + // Test code ... + + await browser.close() +})() +``` + +The full walkthrough is in [Migrate Existing Playwright Tests](/support/docs/migrate-existing-playwright-tests/). For Python, follow [Playwright With Python](/support/docs/python-with-playwright/). For a project that uses `playwright.config.js` and the Playwright test runner, follow [Playwright Test Runner](/support/docs/playwright-test-runner/). + +### Keep Running Testim Tests During the Move + +You can keep running Testim web tests on the Selenium grid while you migrate. In Testim, add a grid of the LambdaTest (now ) type. Enter a grid name, the host (for example, `hub.lambdatest.com`), the port (443 by default), and your Username and Access Key. Then pass the grid name to the Testim CLI with `--grid`. + + + +```bash +testim --label "" --token "" --project "" --grid "" --report-file test-results/testim-tests-report.xml +``` + + + +Testim's docs say this integration supports the Selenium testing option only. For the side, see [Testim Integration](/support/docs/testim-integration/). + +## Step 3: Bring Test Cases Into Test Manager + +Choose the source that matches how your team tracks Testim tests. + +- **TestRail, qTest or Xray.** Testim can link a Testim test to a test case in these tools and send run results there. If your test cases live there, use the one-click importer for [TestRail](/support/docs/one-click-migration-from-testrail/), [qTest](/support/docs/one-click-migration-from-qtest/) or [Xray (Jira Cloud)](/support/docs/one-click-migration-from-xray/). These importers bring in that tool's test cases, not the Testim tests. +- **PDF run reports.** On the Test Case Listing page of your project, click **Generate With AI** and upload the reports, up to 10 files. The [AI Test Case Generator](/support/docs/generate-test-cases-with-ai/) accepts PDFs and writes new test cases from them. Click **Create** to save the ones you keep. +- **CSV file.** If the file lists tests rather than runs, import it with [CSV import](/support/docs/csv-import/) from **Add Test Case > Import CSV**. Mapping at least one CSV header to **Title** is mandatory. Each file can be up to 10 MB. + +## Step 4: Re-create Your Flows in KaneAI + +KaneAI does not run Testim steps, so you re-create each flow in a KaneAI session. + +- **From a test case.** Open a saved test case and click **Automate with KaneAI** in its **Automate** section. A KaneAI session opens with the test case's steps filled in, where you author and run the test. [This action](/support/docs/manual-test-case-creation/#automate-with-kaneai) works on one test case at a time, and the test case must have steps or scenarios. +- **From the generator.** **Create and Automate** saves the generated test cases you select and sends them to KaneAI for automated authoring. It is an experimental feature, so review the steps afterwards. +- **From scratch.** Start a [web test](/support/docs/kane-ai-web-test/) or an [app test](/support/docs/kane-ai-app-test/) and write each step in natural language. [Manual Interaction](/support/docs/kaneai-manual-interaction/) also records your clicks, typing, scrolls and navigation as steps. It cannot record hover actions or checks, and it does not capture mobile browsers. Write those as instructions. + +Re-create Testim features with their KaneAI counterparts: + +- **Groups and shared steps:** build a [module](/support/docs/kane-ai-modules/) once and import it into other tests. +- **Test data and data-driven tests:** use [parameters](/support/docs/kane-ai-using-parameters/) and [datasets](/support/docs/kane-ai-using-datasets/). A dataset can import rows from a CSV file. +- **Custom JavaScript steps:** add a [JavaScript step](/support/docs/kane-ai-javascript-execution/) from the `/` menu. +- **Conditions:** add an [If / Else block](/support/docs/kaneai-conditional-logic/). +- **Visual validations:** add a [Visual Comparison](/support/docs/kaneai-smartui-visual-testing/) step. Its screenshots go to your SmartUI project. +- **API steps:** paste a curl command into an [API step](/support/docs/kane-ai-api-testing/). +- **MySQL and MongoDB validations:** add a [database connection](/support/docs/kaneai-database/) and query it from the test. + + + +When a test is saved as **Ready**, meaning every step has run and passed, KaneAI generates code. In Classic, Selenium Python and Appium Python are available by default. Classic also offers Selenium Java and Playwright Python, C# and JavaScript on request. In New Experience, which is being rolled out in phases, Playwright Python and JavaScript are available. See [KaneAI Automation Code Generation](/support/docs/kane-ai-automation-code-generation/). + +## Step 5: Run Your KaneAI Tests + +1. In your project, open **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 the test cases and set their configurations. +4. Save the run, click **Run on HyperExecute**, and choose **Run Instances Now** or **Schedule Test Run**. + +See [Execute Test Runs on HyperExecute](/support/docs/kaneai-hyperexecute-test-run-execution/). + +With the **KaneAI** toggle on, a configuration can use Desktop or Real Device. [Configurations](/support/docs/test-runs-configurations/) set these limits: + +- Native app testing on Real Devices is available only for KaneAI-generated test runs. +- Mobile browser testing on Real Devices is available for non-KaneAI test runs only. +- Virtual Mobile configurations are available for non-KaneAI test runs only. + +To run from CI tools such as GitHub Actions or Jenkins, copy the Test Run ID from the test run URL. Send it in a POST request to `https://test-manager-api.lambdatest.com/api/atm/v1/hyperexecute`, with your username and access key for Basic Authentication. The call starts HyperExecute jobs. See [Test Automation with CI/CD](/support/docs/kaneai-ci-cd-automation/). + +## What Does Not Carry Over + +- **The tests themselves.** KaneAI does not import or convert Testim tests. KaneAI imports tests only from Katalon, for desktop web tests ([Migration from Katalon](/support/docs/one-click-migration-from-katalon/)). +- **Unsupported steps.** Testim says exported Playwright code may need manual adjustments and that some steps may not be supported. +- **Run history.** Results, screenshots and logs stay in Testim. CSV import in Test Manager creates or updates test cases, not runs. +- **Visual baselines.** A KaneAI Visual Comparison step captures a new baseline the first time the test runs. +- **CLI steps.** Testim CLI actions run Node.js scripts in your CLI environment. KaneAI runs JavaScript in the current testing environment, so re-create those checks with API, database or JavaScript steps. +- **Some mobile targets.** KaneAI test runs do not cover mobile browsers on real devices, or emulators and simulators. + + + +## Related migration guides + +- [Migration from Katalon](/support/docs/one-click-migration-from-katalon/): import Katalon Studio desktop web tests into KaneAI. +- [Migrate Existing Playwright Tests](/support/docs/migrate-existing-playwright-tests/): connect Playwright scripts to . +- [One Click Migration from TestRail](/support/docs/one-click-migration-from-testrail/): import TestRail projects. +- [mabl To KaneAI Migration](/support/docs/mabl-to-kaneai-migration-guide/): move from mabl. +- [testRigor To KaneAI Migration](/support/docs/testrigor-to-kaneai-migration-guide/): move from testRigor. +- [UiPath Test Cloud To KaneAI Migration](/support/docs/uipath-test-cloud-to-kaneai-migration-guide/): move from UiPath Test Cloud. diff --git a/docs/testrigor-integration.md b/docs/testrigor-integration.md index 1798b8fc5..d6aa11db8 100644 --- a/docs/testrigor-integration.md +++ b/docs/testrigor-integration.md @@ -178,6 +178,10 @@ In case, you wish to test locally or privately hosted websites, you can select t Integrating <BrandName /> With testRigor +:::info +Moving your tests to KaneAI? The [testRigor to KaneAI migration guide](/support/docs/testrigor-to-kaneai-migration-guide/) shows how to collect your testRigor steps and data and re-create each test in natural language. +::: + --- diff --git a/docs/testrigor-to-kaneai-migration-guide.md b/docs/testrigor-to-kaneai-migration-guide.md new file mode 100644 index 000000000..566e463f9 --- /dev/null +++ b/docs/testrigor-to-kaneai-migration-guide.md @@ -0,0 +1,351 @@ +--- +id: testrigor-to-kaneai-migration-guide +title: How to migrate from testRigor to KaneAI +hide_title: true +sidebar_label: testRigor To KaneAI Migration +description: Plan your testRigor migration to KaneAI. Collect steps with the testRigor MCP server, bring data sets over as CSV, and re-create each test in natural language. +keywords: + - testrigor migration to kaneai + - testrigor to kaneai migration + - migrate from testrigor to kaneai + - how to migrate from testrigor to kaneai + - testrigor mcp server get test case + - testrigor data set csv export + - testrigor reusable rules to kaneai modules +url: https://www.testmuai.com/support/docs/testrigor-to-kaneai-migration-guide/ +site_name: TestMu AI +slug: testrigor-to-kaneai-migration-guide/ +canonical: https://www.testmuai.com/support/docs/testrigor-to-kaneai-migration-guide/ +--- + +import CodeBlock from '@theme/CodeBlock'; +import {YOUR_LAMBDATEST_USERNAME, YOUR_LAMBDATEST_ACCESS_KEY} from "@site/src/component/keys"; + +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; +import BrandName, { BRAND_URL } from '@site/src/component/BrandName'; +import { CookieTrackingSignup } from '@site/src/component/CookieTracking'; +import VerifiedTag from '@site/src/component/verifiedTag'; + + + + + +# Migrating From testRigor To KaneAI +* * * +This guide covers your testRigor migration to KaneAI, the testing agent that builds tests from natural language instructions. The guide covers what to collect from testRigor, where each asset goes on , 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 | 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](/support/docs/kane-cli-testmd/) | +| Run history and execution reports | Stay in testRigor | Export what you need from testRigor first | + + + + + + + + +## Before You Start + +- A account with KaneAI access. Create one on the signup page. +- A Test Manager project for the re-created tests and datasets. +- Your username and access key from Account Settings > [Password & Security](https://www.testmuai.com/login/?redirectTo=https://accounts.lambdatest.com/security/username-accesskey). 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: + + + +```bash +claude mcp add --transport http testrigor https://api2.testrigor.com/api/v1/mcp --header "personal-access-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 (Optional) + +While you re-create tests, testRigor can keep running your existing suite on the cloud through its integration. + +1. In testRigor, go to **Settings** > **Integrations**. Enable the integration, enter your 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 per browser or device. See [testRigor Integration](/support/docs/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](/support/docs/csv-import/). + +## 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](/support/docs/manual-test-case-creation/#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 [web test](/support/docs/kane-ai-web-test/). +- **Mobile Web Testing:** create a [mobile browser test](/support/docs/author-your-first-mobile-browser-test/). KaneAI test runs do not run mobile browsers on Real Devices (see Step 5). Run the test with **Execute test case** after you save it. +- **Native and Hybrid Mobile:** for a native Android or iOS app, create an [app test](/support/docs/kane-ai-app-test/) and upload 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](/support/docs/kane-ai-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](/support/docs/kane-ai-using-variables/) and [Secrets](/support/docs/kane-ai-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](/support/docs/kane-ai-using-datasets/). +- **Authenticator-app 2FA:** Create a TOTP variable from the Base32 secret key, then use `{{totp.variable_name}}` in a step. See [TOTP Authentication](/support/docs/kaneai-totp/). + +### 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](/support/docs/kaneai-kb-api-testing-and-network-assertions/). See [API Testing](/support/docs/kane-ai-api-testing/). + + + + + +```text +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 +``` + + + + + +```bash +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](/support/docs/kane-ai-automation-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](/support/docs/kaneai-hyperexecute-test-run-execution/). + +With the **KaneAI** toggle on, test run configurations offer **Desktop** and **Real Device**. As [Configurations](/support/docs/test-runs-configurations/) states: + +- "Native app testing on Real Devices is available only for KaneAI-generated test runs." +- "Mobile browser testing on Real Devices is available for non-KaneAI test runs only." +- "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 username and access key. See [Test Automation with CI/CD](/support/docs/kaneai-ci-cd-automation/). + +In place of testRigor's localhost tunnel, KaneAI supports tunneling for websites hosted locally or behind a firewall. See [Geolocation, Tunnel and Proxy](/support/docs/kane-ai-geolocation-tunnel-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](/support/docs/kane-ai-automation-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](/support/docs/kaneai-totp/) generate authenticator-app codes from a shared secret key. +- **Mobile browser runs on real devices.** Per [Configurations](/support/docs/test-runs-configurations/), "Mobile browser testing on Real Devices is available for non-KaneAI test runs only." +- **Labels.** testRigor labels do not transfer. Add tags when you save each KaneAI test. + + + +## Related migration guides + +- [Import Test Cases from CSV](/support/docs/csv-import/): load test case titles and steps into Test Manager. +- [Migration from Katalon](/support/docs/one-click-migration-from-katalon/): the one-click importer for Katalon Studio desktop web tests. +- [Testim To KaneAI Migration](/support/docs/testim-to-kaneai-migration-guide/): the matching guide for Testim tests. +- [mabl To KaneAI Migration](/support/docs/mabl-to-kaneai-migration-guide/): the matching guide for mabl tests. +- [Momentic To KaneAI Migration](/support/docs/momentic-to-kaneai-migration-guide/): the matching guide for Momentic tests. +- [Autosana To KaneAI Migration](/support/docs/autosana-to-kaneai-migration-guide/): the matching guide for Autosana flows. diff --git a/docs/uipath-integration.md b/docs/uipath-integration.md index bdcc2ca5a..aeba726b3 100644 --- a/docs/uipath-integration.md +++ b/docs/uipath-integration.md @@ -109,6 +109,8 @@ UiPath is a leading robotic process automation (RPA) platform powered by artific By integrating UiPath with 's real device cloud, you can enhance your mobile test automation. +If you are moving your test cases off UiPath Test Cloud, see the [UiPath Test Cloud to KaneAI migration guide](/support/docs/uipath-test-cloud-to-kaneai-migration-guide/). + ## Integrating UiPath With *** diff --git a/docs/uipath-test-cloud-to-kaneai-migration-guide.md b/docs/uipath-test-cloud-to-kaneai-migration-guide.md new file mode 100644 index 000000000..47c6b1584 --- /dev/null +++ b/docs/uipath-test-cloud-to-kaneai-migration-guide.md @@ -0,0 +1,357 @@ +--- +id: uipath-test-cloud-to-kaneai-migration-guide +title: How to migrate from UiPath Test Cloud to KaneAI +hide_title: true +sidebar_label: UiPath Test Cloud To KaneAI Migration +description: Plan your UiPath Test Cloud migration to KaneAI. Export test cases from UiPath Test Manager, import them with CSV import, and re-create your tests in KaneAI. +keywords: + - uipath test cloud migration to kaneai + - uipath test cloud to kaneai migration + - migrate from uipath test cloud to kaneai + - how to migrate from uipath test cloud to kaneai + - uipath test suite migration to kaneai + - uipath test manager test case export + - uipath tmh file to csv +url: https://www.testmuai.com/support/docs/uipath-test-cloud-to-kaneai-migration-guide/ +site_name: TestMu AI +slug: uipath-test-cloud-to-kaneai-migration-guide/ +canonical: https://www.testmuai.com/support/docs/uipath-test-cloud-to-kaneai-migration-guide/ +--- + +import CodeBlock from '@theme/CodeBlock'; +import {YOUR_LAMBDATEST_USERNAME, YOUR_LAMBDATEST_ACCESS_KEY} from "@site/src/component/keys"; + +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; +import BrandName, { BRAND_URL } from '@site/src/component/BrandName'; +import { CookieTrackingSignup } from '@site/src/component/CookieTracking'; +import VerifiedTag from '@site/src/component/verifiedTag'; + + + + + + + +# Migrating From UiPath Test Cloud To KaneAI +* * * +This guide covers your UiPath Test Cloud migration to KaneAI: how to move test cases into Test Manager and re-create your tests. UiPath Test Suite has evolved into UiPath Test Cloud, UiPath's dedicated platform for application testing. Its testing tools include Studio, Orchestrator, Robot, Test Manager, Autopilot and Agents. + +You move the test cases you keep in UiPath Test Manager into Test Manager. You then re-create your web and native mobile app tests in KaneAI and run them on . + + +[Note: KaneAI does not import or convert UiPath Test Cloud tests. You export test cases from UiPath Test Manager and import them into Test Manager as a CSV file. You then re-create each automated test in KaneAI in natural language.] + + + +*** +## What Moves From UiPath Test Cloud and Where It Goes + +| UiPath Test Cloud asset | Where it goes on | How | +|---|---|---| +| Test cases: name, description, labels, custom field values | Test Manager test cases | Build a CSV file, then use [CSV import](/support/docs/csv-import/) | +| Manual steps and expected results | Steps and outcomes | Export a TMH file and map them to **Steps** and **Outcome** | +| Studio web test cases, low-code (XAML) or coded (C#) | KaneAI web tests | **Automate with KaneAI** on an imported test case with steps, or a new test in natural language | +| Studio test cases for native mobile apps | KaneAI app tests | Re-create each test in natural language | +| Workflows that several test cases invoke | KaneAI modules | Author the shared steps once as a module | +| Excel test data for data-driven test cases | KaneAI datasets | Save it as CSV, then use **Import Data** | +| Test sets and their schedules | KaneAI test runs | Create a test run, then run or schedule it | +| Studio mobile tests that stay in UiPath | real devices | A cloud device in Mobile Device Manager, per [UiPath Integration](/support/docs/uipath-integration/) | + + + +## Before You Start + +- **A account.** Create one on the signup page. Copy your username and access key from Account Settings > [Password & Security](https://www.testmuai.com/login/?redirectTo=https://accounts.lambdatest.com/security/username-accesskey). +- **KaneAI and Test Manager access.** The **Automate with KaneAI** action requires KaneAI access. +- **A UiPath Test Manager license.** Users with a valid Test Manager license can export projects. Availability also depends on your UiPath cloud platform. +- **Custom fields in the target project.** UiPath exports custom field values but not their definitions. Create the fields in Test Manager and link them to the project first. See [System and Custom Fields](/support/docs/system-and-custom-fields/). + +## Step 1: Export Test Cases From UiPath Test Manager + +UiPath Test Manager has two exports for test cases: + +| Export | File | What it carries | +|---|---|---| +| **Export to Excel** | XLSX | Key, name, description, labels, custom field values, manual and automated flags, and created and updated details. Test steps are not in its column list. | +| **Export** | TMH | Test cases and their custom field values. UiPath documents test steps (**Order**, **Action**, **Expected result**) for a project export. | + + + +### Export the Test Case List to Excel + +1. In UiPath Test Manager, open your project and go to **Test Cases**. +2. Apply filters if you want a subset. The export includes all entries from all pages. +3. Select **Export to Excel**. The XLSX file downloads to your default downloads location. + + + +### Export Test Cases as a TMH File + +1. Open your project and go to **Test Cases**. +2. Select the test cases, then select **Export**. +3. Select the **Project export completed** notification to download the TMH file. + + + +A project export can carry test cases with their test steps, plus labels. Select **More Options** on the project, check **Test cases**, **Object labels** and **Custom fields**, and select **Export**. Its download link expires in seven days. + +## Step 2: Build the CSV File + +CSV import in Test Manager reads a valid `.csv` file of up to 10 MB, so split larger files. + +### From the Excel Export + +Open the XLSX file and save it as **CSV UTF-8 (Comma delimited)**, which keeps accented and non-Latin characters intact. This file has no test steps, so add them in Test Manager after the import. + +### From the TMH File + +A TMH file is a ZIP archive of JSON files. Extract it and use these folders under `objects/`: + +- `testcases`: each test case's `id`, `name`, `description`, `preCondition` and `postCondition`. +- `teststeps`: each step's `testCaseId`, `orderNo`, `description` (the action) and `expectedResult`. The `orderNo` value starts at 0. +- `objectlabels` and `customfieldvalues`: labels and custom field values, linked to a test case by `objectId`. A `labelType` of 1 marks a system label, such as `manual`. Each custom field record holds one `fieldName` and its `fieldValue`, so give each field name its own column. + + + +Write one row per test case. Join the steps to their test case on `testCaseId` and sort them by `orderNo`. Number them from 1 in one cell, indexed like `1. Go to lambdatest.com 2. click on login button`. Combine the expected results the same way. This is the **Test cases use a single row** layout of CSV import. + +The tabs show a test step from the UiPath TMH file format specification and the CSV row it becomes. The name and label come from the same specification. + + + + + +```json +{ + "testSteps": [ + { + "id": "550e8400-e29b-41d4-a716-446655440010", + "testCaseId": "550e8400-e29b-41d4-a716-446655440001", + "orderNo": 0, + "actionType": null, + "description": "Navigate to the login page", + "expectedResult": "Login page is displayed", + "clipboardData": "" + } + ] +} +``` + + + + + +```csv +Title,Steps,Outcome,Tags +Verify login with valid credentials,1. Navigate to the login page,1. Login page is displayed,regression +``` + + + + + + + +## Step 3: Import the CSV File Into Test Manager + +1. In your Test Manager project, go to **Add Test Case > Import CSV**. +2. Upload the file and select **Test cases use a single row**. +3. Map each CSV header to a field. Mapping at least one CSV header to **Title** is mandatory. +4. Map the values, review the preview, and start the import. + +Use these targets for the UiPath columns: + +| From the UiPath export | Map to | +|---|---| +| Name | **Title** | +| Description | **Description** | +| Precondition | **Precondition** | +| Step actions | **Steps** | +| Expected results | **Outcome** | +| Labels | **Tag(s)**, up to 48 characters per tag. If one cell holds several labels, test the import with one row first. | +| Custom field values | Your matching **Custom Fields**, or **Add New Field** | +| Key, postcondition and other columns | A custom field for traceability, or **Ignore Field** | + +See [Import Test Cases from CSV](/support/docs/csv-import/) for every option. + +## Step 4: Re-create Automated Tests in KaneAI + +Studio test cases are low-code XAML files or coded C# test cases, which you publish to Orchestrator as `nupkg` packages. Re-create each one in KaneAI in natural language. + +### Start From a Test Case + +Open an imported test case and click [Automate with KaneAI](/support/docs/manual-test-case-creation/#automate-with-kaneai) in its **Automate** section. A KaneAI session opens, pre-filled with the steps and their expected results. You author and run the test there, one test case at a time. The test case must have steps. + +### Start a New Test + +- Click **Create a Web Test**, or **Create an App Test** to upload an Android or iOS app. See [web tests](/support/docs/kane-ai-web-test/) and [app tests](/support/docs/kane-ai-app-test/). +- Describe each step in natural language. [Manual Interaction](/support/docs/kaneai-manual-interaction/) also records your clicks and typing as steps in desktop browsers, Android apps, and iOS apps in portrait. +- Write each check as an instruction, because Manual Interaction does not record checks. Write a UiPath **Verify Expression** activity as a "verify" step. + +### Reuse Steps and Data + +- **[Modules](/support/docs/kane-ai-modules/):** group a sequence of steps, such as a login flow, into a single reusable unit. +- **[Variables](/support/docs/kane-ai-using-variables/):** store values, such as URLs or credentials, and reuse them in a test case. +- **[Datasets](/support/docs/kane-ai-using-datasets/):** a test that uses parameters gets a Default Dataset. UiPath data-driven tests can read test data from Excel files. Save that data as CSV and add it with **Import Data** in the dataset editor. + +### Generate Test Cases From the Export + +The [AI Test Case Generator](/support/docs/generate-test-cases-with-ai/) accepts CSV, XLSX, JSON and XML files as requirements, up to 10 files of 50 MB each. It writes new test cases from your export, so review them. Its **Create and Automate** option is experimental. + +### Generate Code + +KaneAI generates code for a test saved as **Ready**, where every step has run and passed: + +| Experience | Code you can generate | +|---|---| +| Classic | Selenium Python and Appium Python by default. Selenium Java and Playwright Python, C# and JavaScript on request. | +| New Experience | Playwright Python and Playwright JavaScript. | + +Contact support to enable New Experience or an on-request option. See [KaneAI Automation Code Generation](/support/docs/kane-ai-automation-code-generation/). + +## Step 5: Run Your KaneAI Tests + +Run KaneAI tests through a [test run on HyperExecute](/support/docs/kaneai-hyperexecute-test-run-execution/): + +1. In your Test Manager project, go to **Test Runs** and click **Create Test Run**. Set **Type** to **KaneAI Generated Test Cases**. +2. Add test cases. Only test cases with generated code are available. +3. Give each test case an assignee and at least one configuration, then save the run. +4. Click **Run on HyperExecute** and choose **Run Instances Now** or **Schedule Test Run**. + +When you create a [configuration](/support/docs/test-runs-configurations/) with the **KaneAI** toggle on, the available platforms are **Desktop** and **Real Device**. Native app testing on Real Devices is available only for KaneAI-generated test runs. Mobile browser testing on Real Devices and Virtual Mobile configurations are available for non-KaneAI test runs only. + +To start a run from [CI/CD](/support/docs/kaneai-ci-cd-automation/), such as GitHub Actions or Jenkins, copy the Test Run ID from the test run URL. Send it as `test_run_id` in a POST request to `https://test-manager-api.lambdatest.com/api/atm/v1/hyperexecute`. Use your username and access key for Basic Authentication. + +For websites hosted locally or behind a firewall, KaneAI supports [tunneling](/support/docs/kane-ai-geolocation-tunnel-proxy/). + +## What Does Not Carry Over + +- **Studio test cases and packages.** They run on UiPath robots, from packages you publish to Orchestrator. Re-create them in KaneAI. +- **Automation links.** A TMH export can carry links between test cases and Orchestrator automations. Those links stay in UiPath. +- **Test results and execution logs.** UiPath Test Manager exports all test executions to Excel, or one execution to PDF. Keep those files as your record. +- **Custom field definitions.** Create the fields in before you import. +- **Requirements and their links.** If they are Jira issues, add the issue keys in a column and map it to **Link Jira**. +- **Attachments.** A CSV file carries text only, so upload the attachments you still need. + + + +## Related migration guides + +- [UiPath Integration](/support/docs/uipath-integration/): run UiPath Studio mobile tests on real devices. +- [Import Test Cases from CSV](/support/docs/csv-import/): every option of the CSV import. +- [Migrating from Zephyr Enterprise to Test Manager](/support/docs/migrate-from-zephyr-enterprise/): another migration through CSV import. +- [Migration from Katalon](/support/docs/one-click-migration-from-katalon/): import Katalon Studio desktop web test cases into KaneAI. +- [Testim To KaneAI Migration](/support/docs/testim-to-kaneai-migration-guide/): move from Testim to KaneAI. diff --git a/sidebars.js b/sidebars.js index 8bf013a8f..0daa1817e 100644 --- a/sidebars.js +++ b/sidebars.js @@ -3822,6 +3822,56 @@ module.exports = { label: "Legacy Platform To TestMu AI Migration", id: "migrate-legacy-lambdatest", }, + { + type: "doc", + label: "BrowserStack To KaneAI Migration", + id: "browserstack-to-kaneai-migration-guide", + }, + { + type: "doc", + label: "Sauce Labs To KaneAI Migration", + id: "saucelabs-to-kaneai-migration-guide", + }, + { + type: "doc", + label: "Autosana To KaneAI Migration", + id: "autosana-to-kaneai-migration-guide", + }, + { + type: "doc", + label: "mabl To KaneAI Migration", + id: "mabl-to-kaneai-migration-guide", + }, + { + type: "doc", + label: "Momentic To KaneAI Migration", + id: "momentic-to-kaneai-migration-guide", + }, + { + type: "doc", + label: "Parasoft To KaneAI Migration", + id: "parasoft-to-kaneai-migration-guide", + }, + { + type: "doc", + label: "Tester Army To KaneAI Migration", + id: "tester-army-to-kaneai-migration-guide", + }, + { + type: "doc", + label: "Testim To KaneAI Migration", + id: "testim-to-kaneai-migration-guide", + }, + { + type: "doc", + label: "testRigor To KaneAI Migration", + id: "testrigor-to-kaneai-migration-guide", + }, + { + type: "doc", + label: "UiPath Test Cloud To KaneAI Migration", + id: "uipath-test-cloud-to-kaneai-migration-guide", + }, ], ], From de247d98b88fb049c5eb57ebe3d4cfca9da8dab0 Mon Sep 17 00:00:00 2001 From: VishalLT Date: Fri, 16 Oct 2026 15:39:56 +0530 Subject: [PATCH 3/4] static docs: regenerate for KaneAI migration guides Co-Authored-By: Claude Opus 5.5 --- static/docs/browserstack-to-testmu-migration-guide.md | 2 ++ static/docs/llms.txt | 10 ++++++++++ static/docs/migrate-appium-tests-from-sauce-labs.md | 3 +++ static/docs/migrate-selenium-test-suite.md | 2 ++ static/docs/saucelabs-to-testmu-migration-guide.md | 1 + static/docs/testim-integration.md | 2 ++ static/docs/testmu-capability-map.md | 4 ++-- static/docs/testrigor-integration.md | 2 ++ static/docs/uipath-integration.md | 2 ++ 9 files changed, 26 insertions(+), 2 deletions(-) diff --git a/static/docs/browserstack-to-testmu-migration-guide.md b/static/docs/browserstack-to-testmu-migration-guide.md index 01dbaa8b0..363bc6369 100644 --- a/static/docs/browserstack-to-testmu-migration-guide.md +++ b/static/docs/browserstack-to-testmu-migration-guide.md @@ -6,6 +6,8 @@ TestMu AI and BrowserStack both offer the cloud-based Selenium Grid. Hence, you [Note: This guide covers the migration of tests running on the cloud grid that uses Selenium 4 and Selenium 3] +To run Low Code Automation tests, import Test Management test cases or re-create flows in KaneAI, see the [BrowserStack to KaneAI migration guide](/support/docs/browserstack-to-kaneai-migration-guide/). + ## Authentication Firstly, you need to change the authentication in your configuration settings of your test suite. For running tests on TestMu AI Selenium Grid, you need to have a valid user_name and access_key to perform tests on our Grid. In case you do not have an account on TestMu AI, visit the TestMu AI signup page and create a new account. diff --git a/static/docs/llms.txt b/static/docs/llms.txt index 515890241..6fe833b44 100644 --- a/static/docs/llms.txt +++ b/static/docs/llms.txt @@ -520,9 +520,19 @@ OpenAPI: https://www.testmuai.com/support/docs/OpenAPI.md - [How To Mark As Bug In Responsive Testing | TestMu AI](https://www.testmuai.com/support/docs/mark-as-bug-in-responsive-testing.md): Perform responsive testing with TestMu AI and mark your UI bugs in just a single click. Share them with your colleagues on respective project management tool such as Jira, Trello, Paymo, and more. - [How to Mask Sensitive Data in Selenium on TestMu AI](https://www.testmuai.com/support/docs/selenium-mask-your-data.md): Mask sensitive data in Selenium tests on TestMu AI to hide credentials and personal information from logs and network data. - [How to Migrate Existing Playwright Tests to TestMu AI](https://www.testmuai.com/support/docs/migrate-existing-playwright-tests.md): Migrate existing Playwright test scripts from your local grid to TestMu AI by connecting to the CDP endpoint and passing browser and OS capabilities. +- [How to migrate from Autosana to KaneAI](https://www.testmuai.com/support/docs/autosana-to-kaneai-migration-guide.md): Export Autosana flows with the Autosana CLI, import them into Test Manager through CSV, then re-create and run them as KaneAI app tests on real devices. +- [How to migrate from BrowserStack to KaneAI](https://www.testmuai.com/support/docs/browserstack-to-kaneai-migration-guide.md): Run BrowserStack scripts and exported Low Code Automation tests on TestMu AI, import Test Management CSVs into Test Manager, and re-create flows in KaneAI. - [How to migrate from BrowserStack to TestMu AI](https://www.testmuai.com/support/docs/browserstack-to-testmu-migration-guide.md): Using this guide, you can seamlessly migrate from BrowserStack to TestMu AI. It showcases a hands-on implementation using which you can run tests on TestMu AI (within few minutes) - [How to Migrate From Legacy Test Execution Platform to TestMu AI](https://www.testmuai.com/support/docs/migrate-from-legacy-platform-to-testmu.md): Learn how to migrate from legacy test execution platform to TestMu AI cloud platform. +- [How to migrate from mabl to KaneAI](https://www.testmuai.com/support/docs/mabl-to-kaneai-migration-guide.md): Migrate from mabl to KaneAI. Export mabl tests as Playwright or Selenium IDE code, run them on TestMu AI, import a CSV into Test Manager, re-create flows. +- [How to migrate from Momentic to KaneAI](https://www.testmuai.com/support/docs/momentic-to-kaneai-migration-guide.md): Move from Momentic to KaneAI. Collect your YAML tests, run any ejected Playwright code on TestMu AI, and re-create each test in KaneAI in natural language. +- [How to migrate from Parasoft to KaneAI](https://www.testmuai.com/support/docs/parasoft-to-kaneai-migration-guide.md): Run Parasoft Selenic tests on the TestMu AI Selenium grid, bring test cases into Test Manager, and re-create web flows and SOAtest API calls in KaneAI. +- [How to migrate from Sauce Labs to KaneAI](https://www.testmuai.com/support/docs/saucelabs-to-kaneai-migration-guide.md): Run your Sauce Labs Selenium, Appium and saucectl scripts on TestMu AI, bring test cases into Test Manager, and re-create Sauce AI tests and flows in KaneAI. - [How to migrate from Sauce Labs to TestMu AI](https://www.testmuai.com/support/docs/saucelabs-to-testmu-migration-guide.md): Using this guide, you can seamlessly migrate from Sauce Labs to TestMu AI. It showcases a hands-on implementation using which you can run tests on TestMu AI (within few minutes) +- [How to migrate from Tester Army to KaneAI](https://www.testmuai.com/support/docs/tester-army-to-kaneai-migration-guide.md): Retrieve Tester Army test steps with its CLI or API, import them into Test Manager through CSV, then re-create and run them as KaneAI or Kane CLI tests. +- [How to migrate from Testim to KaneAI](https://www.testmuai.com/support/docs/testim-to-kaneai-migration-guide.md): Move from Testim to KaneAI. Export Testim tests as Playwright code, run them on TestMu AI, bring test cases into Test Manager and re-create flows in KaneAI. +- [How to migrate from testRigor to KaneAI](https://www.testmuai.com/support/docs/testrigor-to-kaneai-migration-guide.md): Move testRigor tests to KaneAI. Collect steps with the testRigor MCP server, bring data sets over as CSV, and re-create each test in natural language. +- [How to migrate from UiPath Test Cloud to KaneAI](https://www.testmuai.com/support/docs/uipath-test-cloud-to-kaneai-migration-guide.md): Export test cases from UiPath Test Manager, import them into TestMu AI Test Manager with CSV import, and re-create your web and mobile app tests in KaneAI. - [How to Migrate Your Selenium Suite to TestMu AI](https://www.testmuai.com/support/docs/migrate-selenium-test-suite.md): Migrate your existing Selenium test suite to the TestMu AI cloud grid with minimal code changes across 10,000+ browser and OS combinations. - [How to perform Accessibility testing using Deque's axe](https://www.testmuai.com/support/docs/deque-integration.md): A quick guide to perform Automated Accessibility testing using Deque's axe across 3000+ browsers and OS combinations. - [How to Perform API Testing With Karate on HyperExecute](https://www.testmuai.com/support/docs/hyperexecute-karate-testing.md): Run Karate API tests, with in-run mock servers, in parallel on HyperExecute. Set your credentials, configure HyperExecute.yaml, and trigger a cloud run. diff --git a/static/docs/migrate-appium-tests-from-sauce-labs.md b/static/docs/migrate-appium-tests-from-sauce-labs.md index 356d46096..c5d5d5b4a 100644 --- a/static/docs/migrate-appium-tests-from-sauce-labs.md +++ b/static/docs/migrate-appium-tests-from-sauce-labs.md @@ -374,4 +374,7 @@ def run_session(desired_cap): driver = webdriver.Remote(command_executor="https://LT_USERNAME:LT_ACCESS_KEY@mobile-hub.lambdatest.com/wd/hub", desired_capabilities=desired_cap) ``` + +To re-create your Appium flows as KaneAI app tests in natural language, follow the [Sauce Labs to KaneAI migration guide](/support/docs/saucelabs-to-kaneai-migration-guide/). + >That’s all about Sauce Labs to TestMu AI migration. In case you have any questions or need any additional information, you could reach out at our **24X7 Chat Support** or mail us directly at support@testmuai.com. diff --git a/static/docs/migrate-selenium-test-suite.md b/static/docs/migrate-selenium-test-suite.md index ecc63b93c..2344e622c 100644 --- a/static/docs/migrate-selenium-test-suite.md +++ b/static/docs/migrate-selenium-test-suite.md @@ -39,6 +39,8 @@ If you are moving from BrowserStack or Sauce Labs, use these dedicated migration - [Migrate from BrowserStack to TestMu AI](/support/docs/browserstack-to-testmu-migration-guide/) - hub URL, capability mapping, and feature equivalents - [Migrate from Sauce Labs to TestMu AI](/support/docs/saucelabs-to-testmu-migration-guide/) - hub URL, capability mapping, and feature equivalents +Running Parasoft Selenic tests? The [Parasoft to KaneAI migration guide](/support/docs/parasoft-to-kaneai-migration-guide/) shows how to run them on the grid with Selenic still attached, and how to re-create them in KaneAI. + ## Prerequisites Make sure you have the following set up before you start. diff --git a/static/docs/saucelabs-to-testmu-migration-guide.md b/static/docs/saucelabs-to-testmu-migration-guide.md index a34dd202f..a3f5f5301 100644 --- a/static/docs/saucelabs-to-testmu-migration-guide.md +++ b/static/docs/saucelabs-to-testmu-migration-guide.md @@ -300,3 +300,4 @@ Visit TestMu AI Web Automation dashboard to view your test execution result. ## Related migration guides - [Migrate Appium Tests from Sauce Labs](/support/docs/migrate-appium-tests-from-sauce-labs/) — move your Appium mobile test suite from Sauce Labs to TestMu AI. +- [Sauce Labs to KaneAI migration guide](/support/docs/saucelabs-to-kaneai-migration-guide/): bring test cases into Test Manager and re-create Sauce AI tests in KaneAI. diff --git a/static/docs/testim-integration.md b/static/docs/testim-integration.md index 082772df0..c352b8c1b 100644 --- a/static/docs/testim-integration.md +++ b/static/docs/testim-integration.md @@ -6,6 +6,8 @@ Testim provides an automated testing platform to create stable tests using AI Na Integrating TestMu AI with Testim lets you run Testim automated tests on TestMu AI cloud-based grid across 3000+ real browsers and OS. +If you plan to move off Testim, the [Testim to KaneAI migration guide](/support/docs/testim-to-kaneai-migration-guide/) shows what Testim can export and how to re-create tests in KaneAI. + ## Prerequisites - Create an account on Testim. - Create a TestMu AI account. You can [sign up for free](https://www.testmuai.com/register/?redirectTo=https://accounts.lambdatest.com/dashboard). diff --git a/static/docs/testmu-capability-map.md b/static/docs/testmu-capability-map.md index 0c84ac4b7..1060eb85a 100644 --- a/static/docs/testmu-capability-map.md +++ b/static/docs/testmu-capability-map.md @@ -80,7 +80,7 @@ ltOptions.put("w3c", true); browserOptions.setCapability("LT:Options", ltOptions); ``` -To migrate your test suites from BrowserStack, checkout this guide on [Migrating from BrowserStack to TestMu AI](/support/docs/browserstack-to-testmu-migration-guide/). +To migrate your test suites from BrowserStack, checkout this guide on [Migrating from BrowserStack to TestMu AI](/support/docs/browserstack-to-testmu-migration-guide/). To move Low Code Automation tests and Test Management test cases, or re-create flows in KaneAI, see the [BrowserStack to KaneAI migration guide](/support/docs/browserstack-to-kaneai-migration-guide/). ## Migrating from Sauce Labs to TestMu AI @@ -114,6 +114,6 @@ ltOptions.put("w3c", true); browserOptions.setCapability("LT:Options", ltOptions); ``` -To migrate your test suites from Sauce Labs, checkout this guide on [Migrating from Sauce Labs to TestMu AI](/support/docs/saucelabs-to-testmu-migration-guide/). +To migrate your test suites from Sauce Labs, checkout this guide on [Migrating from Sauce Labs to TestMu AI](/support/docs/saucelabs-to-testmu-migration-guide/). To re-create your Sauce AI tests and test cases in KaneAI, follow the [Sauce Labs to KaneAI migration guide](/support/docs/saucelabs-to-kaneai-migration-guide/). To generate capabilities use [TestMu AI Capabilities Generator](https://www.testmuai.com/capabilities-generator/) to define key automation testing parameters, such as browser, version, operating system, and additional test settings. diff --git a/static/docs/testrigor-integration.md b/static/docs/testrigor-integration.md index d6e93b08c..bd8571ef1 100644 --- a/static/docs/testrigor-integration.md +++ b/static/docs/testrigor-integration.md @@ -45,3 +45,5 @@ In case, you wish to test locally or privately hosted websites, you can select t > The below test case demonstrates TestMu AI Selenium Automation's booking a demo functionality. First, it visits the TestMu AI Selenium Automation website, clicks on the "Book A Demo" button, enters the required fields and then presses the "Schedule Demo" button. 3. Now visit the TestMu AI Automation Dashboard to view your test execution results. + +Moving your tests to KaneAI? The [testRigor to KaneAI migration guide](/support/docs/testrigor-to-kaneai-migration-guide/) shows how to collect your testRigor steps and data and re-create each test in natural language. diff --git a/static/docs/uipath-integration.md b/static/docs/uipath-integration.md index b1d7dc668..498042b8d 100644 --- a/static/docs/uipath-integration.md +++ b/static/docs/uipath-integration.md @@ -6,6 +6,8 @@ UiPath is a leading robotic process automation (RPA) platform powered by artific By integrating UiPath with TestMu AI's real device cloud, you can enhance your mobile test automation. +If you are moving your test cases off UiPath Test Cloud, see the [UiPath Test Cloud to KaneAI migration guide](/support/docs/uipath-test-cloud-to-kaneai-migration-guide/). + ## Integrating UiPath With TestMu AI **Step 1:** Log in to your UiPath account. From the right side, click on **Download Studio Desktop**. From fd92e7d9ee6acfde64e8c7dc9699ef2a2fca338c Mon Sep 17 00:00:00 2001 From: VishalLT Date: Fri, 16 Oct 2026 16:03:13 +0530 Subject: [PATCH 4/4] accelq migration --- docs/accelq-integration.md | 2 + docs/accelq-to-kaneai-migration-guide.md | 320 ++++++++++++++++++ docs/testim-to-kaneai-migration-guide.md | 1 + docs/testrigor-to-kaneai-migration-guide.md | 1 + ...th-test-cloud-to-kaneai-migration-guide.md | 1 + sidebars.js | 5 + static/docs/accelq-integration.md | 2 + static/docs/llms.txt | 21 +- 8 files changed, 343 insertions(+), 10 deletions(-) create mode 100644 docs/accelq-to-kaneai-migration-guide.md diff --git a/docs/accelq-integration.md b/docs/accelq-integration.md index b00f4c109..6044bd796 100644 --- a/docs/accelq-integration.md +++ b/docs/accelq-integration.md @@ -105,6 +105,8 @@ ACCELQ is an AI Native Codeless automation testing and management platform. It e By integrating with ACCELQ, you can perform web and mobile app automation on an online device farm of 5000+ real devices and 10,000+ browser/device combinations, and accelerate your end-to-end digital testing efforts. +If you plan to move off ACCELQ, the [ACCELQ to KaneAI migration guide](/support/docs/accelq-to-kaneai-migration-guide/) shows how to keep these tests running while you re-create them in KaneAI. + ## Prerequisites --- diff --git a/docs/accelq-to-kaneai-migration-guide.md b/docs/accelq-to-kaneai-migration-guide.md new file mode 100644 index 000000000..2e1449e09 --- /dev/null +++ b/docs/accelq-to-kaneai-migration-guide.md @@ -0,0 +1,320 @@ +--- +id: accelq-to-kaneai-migration-guide +title: How to migrate from ACCELQ to KaneAI +hide_title: true +sidebar_label: ACCELQ To KaneAI Migration +description: Plan your ACCELQ migration to KaneAI. Export ACCELQ scenarios, import them into Test Manager with CSV import, and re-create your tests in KaneAI. +keywords: + - accelq migration to kaneai + - accelq to kaneai migration + - migrate from accelq to kaneai + - how to migrate from accelq to kaneai + - export accelq scenarios to csv + - export accelq test results + - run accelq tests on testmu ai +url: https://www.testmuai.com/support/docs/accelq-to-kaneai-migration-guide/ +site_name: TestMu AI +slug: accelq-to-kaneai-migration-guide/ +canonical: https://www.testmuai.com/support/docs/accelq-to-kaneai-migration-guide/ +--- + +import CodeBlock from '@theme/CodeBlock'; +import {YOUR_LAMBDATEST_USERNAME, YOUR_LAMBDATEST_ACCESS_KEY} from "@site/src/component/keys"; + +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; +import BrandName, { BRAND_URL } from '@site/src/component/BrandName'; +import { CookieTrackingSignup } from '@site/src/component/CookieTracking'; +import VerifiedTag from '@site/src/component/verifiedTag'; + + + + + + + +# Migrating From ACCELQ To KaneAI +* * * +This guide covers your ACCELQ migration to KaneAI: how to export ACCELQ scenarios, move test cases into Test Manager, and re-create your tests. ACCELQ is a cloud-based continuous testing platform for functional and API testing. Its product lines are Automate Web, Automate API, Automate Mobile and ACCELQ Manual. + +ACCELQ and already work together. You can keep running ACCELQ tests on browsers and real devices while you re-create them in KaneAI. + + +[Note: KaneAI does not import or convert ACCELQ tests. You export scenarios from ACCELQ and import them into Test Manager as a CSV file. You then re-create each automated test in KaneAI in natural language.] + + + +*** +## What Moves From ACCELQ and Where It Goes + +| ACCELQ asset | Where it goes on | How | +|---|---|---| +| Automation Scenarios with their steps and custom fields | Test Manager test cases | Export the Scenario list with step details, then use [CSV import](/support/docs/csv-import/) | +| Manual Scenarios: steps and expected results | Test Manager test cases | Export a manual test run as a PDF with step-level detail, then use the AI Test Case Generator | +| Web and mobile Scenarios | KaneAI web and app tests | **Automate with KaneAI** on an imported test case with steps, or a new test in natural language | +| Actions that several Scenarios share | KaneAI modules | Author the shared steps once as a module | +| Test Cases (data variations) and Data Pools | KaneAI datasets | Export to Excel, save as CSV, then use **Import Data** | +| REST API calls from Automate API | API steps in KaneAI web tests | Paste each call as a curl command | +| ACCELQ tests you keep running for now | browsers and real devices | The ACCELQ Agent with LambdaTest (now ) as its external provider (Step 2) | + + + +## Before You Start + +- **A account.** Create one on the signup page. Copy your username and access key from Account Settings > [Password & Security](https://www.testmuai.com/login/?redirectTo=https://accounts.lambdatest.com/security/username-accesskey). +- **KaneAI and Test Manager access.** The **Automate with KaneAI** action requires KaneAI access. +- **ACCELQ access.** You need the Navigator **Scenarios** grid and the **Test Results** grid. ACCELQ's docs do not describe a plan or role limit for the Scenario export. +- **The ACCELQ Agent Dashboard.** You need it only for Step 2. +- **Custom fields in the target project.** Create the fields in Test Manager and link them to the project first. See [System and Custom Fields](/support/docs/system-and-custom-fields/). + +## Step 1: Export Your ACCELQ Scenarios and Data + +ACCELQ exports entities from its Navigator grids, in Excel or CSV. + +### Export Automation Scenarios + +1. In ACCELQ, open **Navigator** and go to the **Scenarios** grid. +2. Click the **Export** icon. +3. Choose **Scenarios list with step details**. Choose **Scenario list with steps and Test Cases** if you also want the data. +4. Select the custom fields to include for Scenarios and Test Cases. + +Grouping by a field such as Status splits the output into one sheet or file per value. + +ACCELQ's docs do not list the column names of this export. Open the file and check them before you build the CSV. + +### Export Test Case Data and Data Pools + +- **Test Cases.** In ACCELQ, a Test Case is one complete set of values for a Scenario's parameters. Open the **Test Cases** tab of a Scenario and export the grid to Excel. +- **Data Pools.** Open the pool and export it to `.xlsx`. Encrypted columns export as headers only, with no values. + +### Export Manual Test Runs + +ACCELQ's docs do not describe an export of Manual Scenarios, but they do describe a test result export. In the **Test Results** grid, select a manual run and choose **Export Results**, then **Export as PDF**. Choose **Step-level detail** to include each test case's steps with their expected results. + +## Step 2: Keep Running ACCELQ Tests on While You Move + +This step is optional. ACCELQ runs tests through the ACCELQ Agent, which can use LambdaTest (now ) as an external provider. The browser runs remotely on . You continue to manage execution and results in ACCELQ. + +1. Open your ACCELQ Agent Dashboard and click **Edit Configuration** on the target agent. +2. Select the external provider option for Web, Mobile, or both. +3. Enter your username and access key, then save and restart the agent. +4. In the ACCELQ **Run** modal, select the agent under **AGENT/HOST**. Then choose the browser or device. + +From the command line, set `web_provider_type=LAMBDATEST` with `web_provider_username` and `web_provider_password`, which takes your access key. Mobile runs use the matching `mobile_provider_` properties. + +See [ACCELQ Integration](/support/docs/accelq-integration/) for the side, including mobile view capture on real devices. To start an ACCELQ CI job on HyperExecute, see [ACCELQ Integration with HyperExecute](/support/docs/hyperexecute-accelq-integration/). + +## Step 3: Import Test Cases Into Test Manager + +CSV import in Test Manager reads a valid `.csv` file of up to 10 MB, so split larger files. + +### Build the CSV File + +If you exported to Excel, save the file as **CSV UTF-8 (Comma delimited)**, which keeps accented and non-Latin characters intact. If the export has several sheets, save each sheet as its own CSV file. Write one row per Scenario. Number its steps from 1 in one cell, indexed like `1. Go to lambdatest.com 2. click on login button`. This is the **Test cases use a single row** layout of CSV import. + +If your export lists each step in its own row, keep that shape. Select **Test cases use multiple rows** during the import instead. + +The example below uses the steps of ACCELQ's own sample Scenario, "Verify Login to QBank". The description and tag are illustrative. + +```csv +Title,Description,Steps,Tags +Verify Login to QBank,Log in and out of QBank,1. Login to QBank 2. Verify home page 3. Logout from QBank,regression +``` + +### Run the Import + +1. In your Test Manager project, go to **Add Test Case > Import CSV**. +2. Upload the file and select the layout that matches it. +3. Map each CSV header to a field. Mapping at least one CSV header to **Title** is mandatory. +4. Map the values, review the preview, and start the import. + +Use these targets for the ACCELQ columns: + +| From the ACCELQ export | Map to | +|---|---| +| Scenario name | **Title** | +| Description | **Description** | +| Steps | **Steps** | +| Tags | **Tag(s)**, up to 48 characters per tag | +| Custom field values | Your matching **Custom Fields**, or **Add New Field** | +| Scenario ID and other columns | A custom field for traceability, or **Ignore Field** | + +See [Import Test Cases from CSV](/support/docs/csv-import/) for every option. + +### Bring In Manual Runs + +On the Test Case Listing page, click **Generate With AI** and upload the PDF reports from Step 1. The [AI Test Case Generator](/support/docs/generate-test-cases-with-ai/) accepts PDFs and spreadsheets, up to 10 files of 50 MB each. It writes new test cases from them, so review them before you save. + +## Step 4: Re-create Your Tests in KaneAI + +Each ACCELQ Scenario step is an Action, a reusable component that holds the step's logic. KaneAI does not run Actions, so re-create each Scenario in natural language. + +### Start From a Test Case + +Open an imported test case and click [Automate with KaneAI](/support/docs/manual-test-case-creation/#automate-with-kaneai) in its **Automate** section. A KaneAI session opens, pre-filled with the steps and their expected results. You author and run the test there, one test case at a time. The test case must have steps. + +### Start a New Test + +- Click **Create a Web Test**, or **Create an App Test** to upload an Android or iOS app. See [web tests](/support/docs/kane-ai-web-test/) and [app tests](/support/docs/kane-ai-app-test/). +- Describe each step in natural language. [Manual Interaction](/support/docs/kaneai-manual-interaction/) also records your clicks and typing as steps in desktop browsers, Android apps, and iOS apps in portrait. +- Write each check as an instruction, because Manual Interaction does not record checks. + +### Reuse Steps and Data + +- **[Modules](/support/docs/kane-ai-modules/):** group a sequence of steps, such as a login flow, into a single reusable unit. Build one for each Action that many Scenarios share. +- **[Parameters](/support/docs/kane-ai-using-parameters/) and [datasets](/support/docs/kane-ai-using-datasets/):** a test that uses parameters gets a Default Dataset. Save your ACCELQ Test Case or Data Pool export as CSV and add it with **Import Data** in the dataset editor. +- **[Secrets](/support/docs/kane-ai-secrets/):** enter encrypted Data Pool values again as secrets, because the export leaves them out. + +### Re-create API Steps + +Automate API covers SOAP and REST services, message services, databases and enterprise message buses. ACCELQ's docs do not describe an export of API test logic. Write each REST call as a curl command, then paste it into an [API step](/support/docs/kane-ai-api-testing/) in a KaneAI web test. For database checks, add a [database connection](/support/docs/kaneai-database/). + +### Generate Code + +KaneAI generates code for a test saved as **Ready**, where every step has run and passed: + +| Experience | Code you can generate | +|---|---| +| Classic | Selenium Python and Appium Python by default. Selenium Java and Playwright Python, C# and JavaScript on request. | +| New Experience | Playwright Python and Playwright JavaScript. | + +Contact support to enable New Experience or an on-request option. See [KaneAI Automation Code Generation](/support/docs/kane-ai-automation-code-generation/). + +## Step 5: Run Your KaneAI Tests + +Run KaneAI tests through a [test run on HyperExecute](/support/docs/kaneai-hyperexecute-test-run-execution/): + +1. In your Test Manager project, go to **Test Runs** and click **Create Test Run**. Set **Type** to **KaneAI Generated Test Cases**. +2. Add test cases. Only test cases with generated code are available. +3. Give each test case an assignee and at least one configuration, then save the run. +4. Click **Run on HyperExecute** and choose **Run Instances Now** or **Schedule Test Run**. + +When you create a [configuration](/support/docs/test-runs-configurations/) with the **KaneAI** toggle on, the available platforms are **Desktop** and **Real Device**. Native app testing on Real Devices is available only for KaneAI-generated test runs. Mobile browser testing on Real Devices and Virtual Mobile configurations are available for non-KaneAI test runs only. + +In ACCELQ, a CI tool runs a CI Job through a plugin, such as the Jenkins plugin, or through ACCELQ's trigger-job REST API. To start a KaneAI run from [CI/CD](/support/docs/kaneai-ci-cd-automation/) instead, copy the Test Run ID from the test run URL. Send it as `test_run_id` in a POST request to `https://test-manager-api.lambdatest.com/api/atm/v1/hyperexecute`. Use your username and access key for Basic Authentication. + +For websites hosted locally or behind a firewall, KaneAI supports [tunneling](/support/docs/kane-ai-geolocation-tunnel-proxy/). + +## What Does Not Carry Over + +- **Actions, Contexts and element repositories.** They hold the logic and elements of your ACCELQ tests and stay in ACCELQ. +- **Desktop, mainframe and message service tests.** Automate Web also covers desktop and mainframe automation, and Automate API covers message services. KaneAI tests web and mobile apps, so keep these tests in ACCELQ. +- **Test results and screenshots.** Export runs to PDF or Excel as your record. Screenshots stay in ACCELQ. +- **Requirement links.** If they are Jira issues, add the issue keys in a column and map it to **Link Jira**. +- **Test Suites and schedules.** Rebuild them as KaneAI test runs. + + + +## Related migration guides + +- [ACCELQ Integration](/support/docs/accelq-integration/): run ACCELQ tests on browsers and real devices. +- [ACCELQ Integration with HyperExecute](/support/docs/hyperexecute-accelq-integration/): run an ACCELQ CI job on HyperExecute. +- [Import Test Cases from CSV](/support/docs/csv-import/): every option of the CSV import. +- [UiPath Test Cloud To KaneAI Migration](/support/docs/uipath-test-cloud-to-kaneai-migration-guide/): move from UiPath Test Cloud to KaneAI. +- [Testim To KaneAI Migration](/support/docs/testim-to-kaneai-migration-guide/): move from Testim to KaneAI. +- [testRigor To KaneAI Migration](/support/docs/testrigor-to-kaneai-migration-guide/): move from testRigor to KaneAI. diff --git a/docs/testim-to-kaneai-migration-guide.md b/docs/testim-to-kaneai-migration-guide.md index 4d7a72f1c..457238948 100644 --- a/docs/testim-to-kaneai-migration-guide.md +++ b/docs/testim-to-kaneai-migration-guide.md @@ -336,3 +336,4 @@ To run from CI tools such as GitHub Actions or Jenkins, copy the Test Run ID fro - [mabl To KaneAI Migration](/support/docs/mabl-to-kaneai-migration-guide/): move from mabl. - [testRigor To KaneAI Migration](/support/docs/testrigor-to-kaneai-migration-guide/): move from testRigor. - [UiPath Test Cloud To KaneAI Migration](/support/docs/uipath-test-cloud-to-kaneai-migration-guide/): move from UiPath Test Cloud. +- [ACCELQ To KaneAI Migration](/support/docs/accelq-to-kaneai-migration-guide/): move from ACCELQ. diff --git a/docs/testrigor-to-kaneai-migration-guide.md b/docs/testrigor-to-kaneai-migration-guide.md index 566e463f9..2501beb79 100644 --- a/docs/testrigor-to-kaneai-migration-guide.md +++ b/docs/testrigor-to-kaneai-migration-guide.md @@ -349,3 +349,4 @@ In place of testRigor's localhost tunnel, KaneAI supports tunneling for websites - [mabl To KaneAI Migration](/support/docs/mabl-to-kaneai-migration-guide/): the matching guide for mabl tests. - [Momentic To KaneAI Migration](/support/docs/momentic-to-kaneai-migration-guide/): the matching guide for Momentic tests. - [Autosana To KaneAI Migration](/support/docs/autosana-to-kaneai-migration-guide/): the matching guide for Autosana flows. +- [ACCELQ To KaneAI Migration](/support/docs/accelq-to-kaneai-migration-guide/): the matching guide for ACCELQ tests. diff --git a/docs/uipath-test-cloud-to-kaneai-migration-guide.md b/docs/uipath-test-cloud-to-kaneai-migration-guide.md index 47c6b1584..8a8120090 100644 --- a/docs/uipath-test-cloud-to-kaneai-migration-guide.md +++ b/docs/uipath-test-cloud-to-kaneai-migration-guide.md @@ -355,3 +355,4 @@ For websites hosted locally or behind a firewall, KaneAI supports [tunneling](/s - [Migrating from Zephyr Enterprise to Test Manager](/support/docs/migrate-from-zephyr-enterprise/): another migration through CSV import. - [Migration from Katalon](/support/docs/one-click-migration-from-katalon/): import Katalon Studio desktop web test cases into KaneAI. - [Testim To KaneAI Migration](/support/docs/testim-to-kaneai-migration-guide/): move from Testim to KaneAI. +- [ACCELQ To KaneAI Migration](/support/docs/accelq-to-kaneai-migration-guide/): move from ACCELQ to KaneAI. diff --git a/sidebars.js b/sidebars.js index 0daa1817e..5401423e0 100644 --- a/sidebars.js +++ b/sidebars.js @@ -3832,6 +3832,11 @@ module.exports = { label: "Sauce Labs To KaneAI Migration", id: "saucelabs-to-kaneai-migration-guide", }, + { + type: "doc", + label: "ACCELQ To KaneAI Migration", + id: "accelq-to-kaneai-migration-guide", + }, { type: "doc", label: "Autosana To KaneAI Migration", diff --git a/static/docs/accelq-integration.md b/static/docs/accelq-integration.md index 6e1155b9d..fff38559c 100644 --- a/static/docs/accelq-integration.md +++ b/static/docs/accelq-integration.md @@ -6,6 +6,8 @@ ACCELQ is an AI Native Codeless automation testing and management platform. It e By integrating TestMu AI with ACCELQ, you can perform web and mobile app automation on an online device farm of 5000+ real devices and 10,000+ browser/device combinations, and accelerate your end-to-end digital testing efforts. +If you plan to move off ACCELQ, the [ACCELQ to KaneAI migration guide](/support/docs/accelq-to-kaneai-migration-guide/) shows how to keep these tests running while you re-create them in KaneAI. + ## Prerequisites 1. Make sure you have a TestMu AI account. If you don't have an account yet, sign up for free. diff --git a/static/docs/llms.txt b/static/docs/llms.txt index 6fe833b44..97e8b099b 100644 --- a/static/docs/llms.txt +++ b/static/docs/llms.txt @@ -520,19 +520,20 @@ OpenAPI: https://www.testmuai.com/support/docs/OpenAPI.md - [How To Mark As Bug In Responsive Testing | TestMu AI](https://www.testmuai.com/support/docs/mark-as-bug-in-responsive-testing.md): Perform responsive testing with TestMu AI and mark your UI bugs in just a single click. Share them with your colleagues on respective project management tool such as Jira, Trello, Paymo, and more. - [How to Mask Sensitive Data in Selenium on TestMu AI](https://www.testmuai.com/support/docs/selenium-mask-your-data.md): Mask sensitive data in Selenium tests on TestMu AI to hide credentials and personal information from logs and network data. - [How to Migrate Existing Playwright Tests to TestMu AI](https://www.testmuai.com/support/docs/migrate-existing-playwright-tests.md): Migrate existing Playwright test scripts from your local grid to TestMu AI by connecting to the CDP endpoint and passing browser and OS capabilities. -- [How to migrate from Autosana to KaneAI](https://www.testmuai.com/support/docs/autosana-to-kaneai-migration-guide.md): Export Autosana flows with the Autosana CLI, import them into Test Manager through CSV, then re-create and run them as KaneAI app tests on real devices. -- [How to migrate from BrowserStack to KaneAI](https://www.testmuai.com/support/docs/browserstack-to-kaneai-migration-guide.md): Run BrowserStack scripts and exported Low Code Automation tests on TestMu AI, import Test Management CSVs into Test Manager, and re-create flows in KaneAI. +- [How to migrate from ACCELQ to KaneAI](https://www.testmuai.com/support/docs/accelq-to-kaneai-migration-guide.md): Plan your ACCELQ migration to KaneAI. Export ACCELQ scenarios, import them into Test Manager with CSV import, and re-create your tests in KaneAI. +- [How to migrate from Autosana to KaneAI](https://www.testmuai.com/support/docs/autosana-to-kaneai-migration-guide.md): Plan your Autosana migration to KaneAI. Export flows with the Autosana CLI, import them into Test Manager through CSV, then re-create them as KaneAI tests. +- [How to migrate from BrowserStack to KaneAI](https://www.testmuai.com/support/docs/browserstack-to-kaneai-migration-guide.md): Plan your BrowserStack migration to KaneAI. Run scripts and exported Low Code Automation tests on TestMu AI, import test cases, and re-create flows in KaneAI. - [How to migrate from BrowserStack to TestMu AI](https://www.testmuai.com/support/docs/browserstack-to-testmu-migration-guide.md): Using this guide, you can seamlessly migrate from BrowserStack to TestMu AI. It showcases a hands-on implementation using which you can run tests on TestMu AI (within few minutes) - [How to Migrate From Legacy Test Execution Platform to TestMu AI](https://www.testmuai.com/support/docs/migrate-from-legacy-platform-to-testmu.md): Learn how to migrate from legacy test execution platform to TestMu AI cloud platform. -- [How to migrate from mabl to KaneAI](https://www.testmuai.com/support/docs/mabl-to-kaneai-migration-guide.md): Migrate from mabl to KaneAI. Export mabl tests as Playwright or Selenium IDE code, run them on TestMu AI, import a CSV into Test Manager, re-create flows. -- [How to migrate from Momentic to KaneAI](https://www.testmuai.com/support/docs/momentic-to-kaneai-migration-guide.md): Move from Momentic to KaneAI. Collect your YAML tests, run any ejected Playwright code on TestMu AI, and re-create each test in KaneAI in natural language. -- [How to migrate from Parasoft to KaneAI](https://www.testmuai.com/support/docs/parasoft-to-kaneai-migration-guide.md): Run Parasoft Selenic tests on the TestMu AI Selenium grid, bring test cases into Test Manager, and re-create web flows and SOAtest API calls in KaneAI. -- [How to migrate from Sauce Labs to KaneAI](https://www.testmuai.com/support/docs/saucelabs-to-kaneai-migration-guide.md): Run your Sauce Labs Selenium, Appium and saucectl scripts on TestMu AI, bring test cases into Test Manager, and re-create Sauce AI tests and flows in KaneAI. +- [How to migrate from mabl to KaneAI](https://www.testmuai.com/support/docs/mabl-to-kaneai-migration-guide.md): Plan your mabl migration to KaneAI. Export mabl tests as Playwright or Selenium IDE code, run them on TestMu AI, import a CSV and re-create flows. +- [How to migrate from Momentic to KaneAI](https://www.testmuai.com/support/docs/momentic-to-kaneai-migration-guide.md): Plan your Momentic migration to KaneAI. Collect your YAML tests, run any ejected Playwright code on TestMu AI, and re-create each test in natural language. +- [How to migrate from Parasoft to KaneAI](https://www.testmuai.com/support/docs/parasoft-to-kaneai-migration-guide.md): Plan your Parasoft migration to KaneAI. Run Selenic tests on the TestMu AI Selenium grid, bring test cases into Test Manager, and re-create flows and API calls. +- [How to migrate from Sauce Labs to KaneAI](https://www.testmuai.com/support/docs/saucelabs-to-kaneai-migration-guide.md): Plan your Sauce Labs migration to KaneAI. Run Selenium, Appium and saucectl scripts on TestMu AI, bring test cases into Test Manager, and re-create flows. - [How to migrate from Sauce Labs to TestMu AI](https://www.testmuai.com/support/docs/saucelabs-to-testmu-migration-guide.md): Using this guide, you can seamlessly migrate from Sauce Labs to TestMu AI. It showcases a hands-on implementation using which you can run tests on TestMu AI (within few minutes) -- [How to migrate from Tester Army to KaneAI](https://www.testmuai.com/support/docs/tester-army-to-kaneai-migration-guide.md): Retrieve Tester Army test steps with its CLI or API, import them into Test Manager through CSV, then re-create and run them as KaneAI or Kane CLI tests. -- [How to migrate from Testim to KaneAI](https://www.testmuai.com/support/docs/testim-to-kaneai-migration-guide.md): Move from Testim to KaneAI. Export Testim tests as Playwright code, run them on TestMu AI, bring test cases into Test Manager and re-create flows in KaneAI. -- [How to migrate from testRigor to KaneAI](https://www.testmuai.com/support/docs/testrigor-to-kaneai-migration-guide.md): Move testRigor tests to KaneAI. Collect steps with the testRigor MCP server, bring data sets over as CSV, and re-create each test in natural language. -- [How to migrate from UiPath Test Cloud to KaneAI](https://www.testmuai.com/support/docs/uipath-test-cloud-to-kaneai-migration-guide.md): Export test cases from UiPath Test Manager, import them into TestMu AI Test Manager with CSV import, and re-create your web and mobile app tests in KaneAI. +- [How to migrate from Tester Army to KaneAI](https://www.testmuai.com/support/docs/tester-army-to-kaneai-migration-guide.md): Plan your Tester Army migration to KaneAI. Retrieve test steps with the Tester Army CLI or API, import them into Test Manager, and re-create them in KaneAI. +- [How to migrate from Testim to KaneAI](https://www.testmuai.com/support/docs/testim-to-kaneai-migration-guide.md): Plan your Testim migration to KaneAI. Export Testim tests as Playwright code, run them on TestMu AI, bring test cases into Test Manager and re-create flows. +- [How to migrate from testRigor to KaneAI](https://www.testmuai.com/support/docs/testrigor-to-kaneai-migration-guide.md): Plan your testRigor migration to KaneAI. Collect steps with the testRigor MCP server, bring data sets over as CSV, and re-create each test in natural language. +- [How to migrate from UiPath Test Cloud to KaneAI](https://www.testmuai.com/support/docs/uipath-test-cloud-to-kaneai-migration-guide.md): Plan your UiPath Test Cloud migration to KaneAI. Export test cases from UiPath Test Manager, import them with CSV import, and re-create your tests in KaneAI. - [How to Migrate Your Selenium Suite to TestMu AI](https://www.testmuai.com/support/docs/migrate-selenium-test-suite.md): Migrate your existing Selenium test suite to the TestMu AI cloud grid with minimal code changes across 10,000+ browser and OS combinations. - [How to perform Accessibility testing using Deque's axe](https://www.testmuai.com/support/docs/deque-integration.md): A quick guide to perform Automated Accessibility testing using Deque's axe across 3000+ browsers and OS combinations. - [How to Perform API Testing With Karate on HyperExecute](https://www.testmuai.com/support/docs/hyperexecute-karate-testing.md): Run Karate API tests, with in-run mock servers, in parallel on HyperExecute. Set your credentials, configure HyperExecute.yaml, and trigger a cloud run.