TestMu AI Selenium Automation Grid enables you to perform end-to-end automation tests on a secure, reliable, and scalable Selenium infrastructure. You can perform automated cross browser testing with Selenium scripts on 3000+ browsers and operating systems environments, giving you higher test coverage and at significantly less built times. TestMu AI will help you evaluate how well your web application renders when accessed through a variety of different browsers.
Features of the TestMu AI Automation Jenkins Plugin:
- Integrate your Jenkins Jobs to run tests on TestMu AI by configuring TestMu AI credentials using the TestMu AI Automation Jenkins Plugin.
- Integrate your freestyle jobs as well as pipeline jobs with TestMu AI using this plugin.
- Set up TestMu AI Tunnel using the TestMu AI Automation Plugin to test your locally hosted web applications or websites.
- View TestMu AI test results on the go after every Jenkins Job run.
- Run natural language browser tests with Kane CLI, in Chrome on the agent or on the TestMu AI HyperExecute grid, with the Run Kane CLI tests (TestMu AI) build step.
- Minimum Jenkins version supported is 1.653+.
- A TestMu AI Account, Sign up now for free if you don't have an existing account on TestMu AI.
- Follow this TestMu AI Automation Jenkins Plugin Documentation to integrate your jenkins freestyle and pipeline job with TestMu AI.
The Run Kane CLI tests (TestMu AI) build step (kaneCli in pipelines) installs Kane CLI, runs one natural language objective or a suite of committed _test.md files, prints a pass/fail verdict with one row per test and the Test Manager link, archives the evidence pack and logs under kane-out/, and fails the build when any test fails.
The agent needs Node.js 20 or later with npm. For local runs the step downloads Chrome stable into the workspace's temporary folder (Linux agents need unzip); untick Install Chrome when Chrome is already installed, or set KANE_CLI_CHROME_PATH.
Choose your TestMu AI credentials in the step, or leave them empty to use the LT_USERNAME and LT_ACCESS_KEY environment variables (for example from the TestMu AI build environment option, withEnv or withCredentials).
Run one objective:
kaneCli credentialsId: 'testmu-ai',
objective: 'Go to https://staging.example.com/cart, click Checkout and verify the page shows Order Summary'
Run every committed test file as one suite with four workers:
kaneCli credentialsId: 'testmu-ai', testFiles: 'tests/**/*_test.md', parallel: 4
Run the suite on the HyperExecute grid (needs HyperExecute on your plan; the agent needs no Chrome):
kaneCli credentialsId: 'testmu-ai', testFiles: 'tests/**/*_test.md', remote: true, parallel: 4
| Option | Description | Default |
|---|---|---|
credentialsId |
TestMu AI credentials. Empty uses LT_USERNAME and LT_ACCESS_KEY. |
|
objective |
Natural language objective, run with kane-cli run. Set this or testFiles. |
|
url |
Start URL for an objective. | |
testFiles |
Ant-style pattern of _test.md files, run as one kane-cli testrun suite. |
|
remote |
Run the testFiles suite on the HyperExecute grid. |
false |
timeout |
Max seconds for an objective. | 300 |
parallel |
Workers for a suite (grid runners with remote). |
1 |
failFast |
Stop a suite after the first failure. | false |
installChrome |
Download Chrome stable for local runs. | true |
kaneVersion |
Version of @testmuai/kane-cli to install. |
latest |
extraArgs |
Extra flags appended to the kane-cli command. | |
archiveResults |
Archive kane-out/ as build artifacts. Open a pack with kane-cli evidence serve <pack>. |
true |
See the Kane CLI guides for CI/CD, batch runs with testrun and remote runs on HyperExecute.