TestMu AI (Formerly LambdaTest) is the world's first full-stack AI Agentic Quality Engineering platform that empowers teams to test intelligently, smarter, and ship faster. Built for scale, it offers a full-stack testing cloud with 10K+ real devices and 3,000+ browsers. With AI-native test management, MCP servers, and agent-based automation, TestMu AI supports Selenium, Appium, Playwright, and all major frameworks.
With TestMu AI (Formerly LambdaTest), you can run Go unit tests on HyperExecute across different platforms with auto-split and matrix execution modes.
- Sign up on TestMu AI (Formerly LambdaTest).
- Follow the TestMu AI documentation (Formerly LambdaTest) for the full setup walkthrough.
Before using HyperExecute, download the HyperExecute CLI binary corresponding to your host OS. Along with it, export the environment variables LT_USERNAME and LT_ACCESS_KEY available from your TestMu AI (Formerly LambdaTest) profile page.
Download HyperExecute CLI
Download the HyperExecute CLI binary for your platform (recommended: place it in the project's parent directory):
- Mac: https://downloads.lambdatest.com/hyperexecute/darwin/hyperexecute
- Linux: https://downloads.lambdatest.com/hyperexecute/linux/hyperexecute
- Windows: https://downloads.lambdatest.com/hyperexecute/windows/hyperexecute.exe
Set your credentials as environment variables.
macOS / Linux:
export LT_USERNAME="YOUR_USERNAME"
export LT_ACCESS_KEY="YOUR_ACCESS_KEY"Windows:
set LT_USERNAME="YOUR_USERNAME"
set LT_ACCESS_KEY="YOUR_ACCESS_KEY"Auto-split execution lets you run tests at predefined concurrency and distribute tests over the available infrastructure. Concurrency can be achieved at different levels — file, module, test suite, test, scenario, etc.
For more information about auto-split execution, check out the TestMu AI documentation.
The auto-split YAML file (.hyperexecute_autosplit.yaml) in the repo contains the following configuration:
globalTimeout: 90
testSuiteTimeout: 90
testSuiteStep: 90Global timeout, testSuite timeout, and testSuite step timeout are set to 90 minutes.
The runson key determines the platform on which the tests are executed. Here it is set to Windows.
runson: winAuto-split is set to true in the YAML file.
autosplit: trueretryOnFailure is set to true, instructing HyperExecute to retry failed commands. The retry operation runs until the number of retries in maxRetries are exhausted or the command results in a pass. Concurrency (number of parallel sessions) is set to 2.
retryOnFailure: true
runson: win
maxRetries: 2To leverage dependency caching in HyperExecute, the integrity of go.exe is checked using the checksum functionality.
cacheKey: '{{ checksum "go.exe" }}'Set the array of files and directories to be cached. In the example, all packages are cached in the C:\Program Files\Go\bin directory.
cacheDirectories:
- C:\Program Files\Go\binThe testDiscovery directive contains the command that gives details of the mode of execution and the command used for test execution. Here, the list of test file scenarios is fetched and passed to testRunnerCommand.
testDiscovery:
type: raw
mode: dynamic
command: |
printf 'golang-hyperexecute-unit-test-sample-repo/Tests/armstrong/\ngolang-hyperexecute-unit-test-sample-repo/Tests/array/\ngolang-hyperexecute-unit-test-sample-repo/Tests/case1/\ngolang-hyperexecute-unit-test-sample-repo/Tests/greet/\ngolang-hyperexecute-unit-test-sample-repo/Tests/Hello/\ngolang-hyperexecute-unit-test-sample-repo/Tests/integer/\ngolang-hyperexecute-unit-test-sample-repo/Tests/multiples/\ngolang-hyperexecute-unit-test-sample-repo/Tests/oops/\ngolang-hyperexecute-unit-test-sample-repo/Tests/palindrome/\ngolang-hyperexecute-unit-test-sample-repo/Tests/repeat/\n'Running the above command on the terminal gives a list of test scenario lines located in the project folder:
golang-hyperexecute-unit-test-sample-repo/Tests/armstrong/
golang-hyperexecute-unit-test-sample-repo/Tests/array/
golang-hyperexecute-unit-test-sample-repo/Tests/case1/
golang-hyperexecute-unit-test-sample-repo/Tests/greet/
golang-hyperexecute-unit-test-sample-repo/Tests/Hello/
golang-hyperexecute-unit-test-sample-repo/Tests/integer/
golang-hyperexecute-unit-test-sample-repo/Tests/multiples/
golang-hyperexecute-unit-test-sample-repo/Tests/oops/
golang-hyperexecute-unit-test-sample-repo/Tests/palindrome/
golang-hyperexecute-unit-test-sample-repo/Tests/repeat/
The testRunnerCommand contains the command used for triggering the test. The output from testDiscovery acts as input to the test runner.
testRunnerCommand: go test $test -coverpkg=$test -coverprofile=coverage/profile.txtThe mergeArtifacts directive (default: false) is set to true for merging artifacts generated under each task.
The uploadArtefacts directive instructs HyperExecute to upload artifacts (files, reports, etc.) generated after task completion. In the example, path contains a regex for parsing the directory that contains test reports.
mergeArtifacts: true
uploadArtefacts:
- name: Reports
path:
- coverage/**HyperExecute also lets you download the artifacts to your local machine. Click on the Artifacts button corresponding to the associated TestID.
./hyperexecute --config --verbose .hyperexecute_autosplit.yamlView results on your TestMu AI dashboard.
Matrix-based test execution runs the same tests across different test or input combinations. The Matrix directive in HyperExecute YAML file is a key:value pair where value is an array of strings.
For more information about matrix multiplexing, check out the TestMu AI documentation.
The matrix YAML file (.hyperexecute_matrix.yaml) in the repo contains the following configuration:
globalTimeout: 90
testSuiteTimeout: 90
testSuiteStep: 90The target platform is set to Windows. Set the runson key to win if the tests have to be executed on the Windows platform.
runson: winTest files in the Tests folder contain the test scenarios to run on the HyperExecute grid. Tests run in parallel based on the specified input combinations.
matrix:
os: [win]
files: ["golang-hyperexecute-unit-test-sample-repo/Tests/armstrong", "golang-hyperexecute-unit-test-sample-repo/Tests/array", "golang-hyperexecute-unit-test-sample-repo/Tests/case1", "golang-hyperexecute-unit-test-sample-repo/Tests/greet", "golang-hyperexecute-unit-test-sample-repo/Tests/Hello", "golang-hyperexecute-unit-test-sample-repo/Tests/integer", "golang-hyperexecute-unit-test-sample-repo/Tests/multiples", "golang-hyperexecute-unit-test-sample-repo/Tests/oops", "golang-hyperexecute-unit-test-sample-repo/Tests/palindrome", "golang-hyperexecute-unit-test-sample-repo/Tests/repeat"]The testSuites object contains a list of commands. The go test command is used to run tests in .go files. Tags are mentioned as an array to the files key that is a part of the matrix.
testSuites:
- go test $files -cover -coverpkg=$files -coverprofile=coverage/profile.txtDependency caching is enabled in the YAML file to ensure package dependencies are not re-downloaded in subsequent runs.
cacheKey: '{{ checksum "go.exe" }}'Set the array of files and directories to be cached.
cacheDirectories:
- C:\Program Files\Go\binSteps that must run before test execution are listed in the pre run step.
pre:
- curl -O https://dl.google.com/go/go1.20.3.windows-amd64.msimergeArtifacts: true
uploadArtefacts:
- name: Reports
path:
- coverage/**./hyperexecute --config --verbose .hyperexecute_matrix.yamlRun the following command on the terminal to trigger tests on Windows:
./hyperexecute.exe --config --verbose .hyperexecute_autosplit.yamlRun the following command on the terminal to trigger tests on Linux:
./hyperexecute --config --verbose .hyperexecute_autosplit.yamlTo use secret keys in the YAML file, set them by clicking on the Secrets button on the dashboard. Create an environment variable that uses the secret key:
env:
AccessKey: ${{.secrets.AccessKey}}HyperExecute lets you navigate between Test Logs in the Automation Dashboard and HyperExecute Logs. You get relevant test details like video, network log, commands, exceptions, and more in the dashboard.
Contributions are welcome. Open an issue to discuss your idea before submitting a pull request. When reporting bugs, include your Go version, OS, and HyperExecute CLI version.
Connect with testers and developers in the TestMu AI Community. Ask questions, share what you are building, and discuss best practices in test automation and DevOps.
Earn free TestMu AI Certifications for testers, developers, and QA engineers. Validate your skills in Selenium, Cypress, Playwright, Appium, Espresso and more. Industry-recognized, shareable on LinkedIn, and built by practitioners, not marketers.
Learn modern testing through tutorials, guides, videos, and weekly updates:
On January 12, 2026, LambdaTest evolved to TestMu AI, the world's first fully autonomous Agentic AI Quality Engineering Platform.
Same team. Same infrastructure. Same customer accounts. All existing LambdaTest logins, scripts, capabilities, and integrations continue to work without change.
👉 Find the new home for LambdaTest.
In 2017, we launched LambdaTest with a simple mission: make testing fast, reliable, and accessible. As LambdaTest grew, we expanded into Test Intelligence, Visual Regression Testing, Accessibility Testing, API Testing, and Performance Testing, covering the full depth of the testing lifecycle.
As software development entered the AI era, testing had to evolve, too. We rebuilt the architecture to be AI-native from the ground up, with autonomous agents that plan, author, execute, analyze, and optimize tests while keeping humans in the loop. The platform integrates with your repos, CI, IDEs, and terminals, continuously learning from every code change and development signal.
That evolution earned a new name: TestMu AI, built for an AI-first future of quality engineering. TestMu is not a new name for us. It is the name of our annual community conference, which has brought together 100,000+ quality engineers to discuss how AI would reshape testing, long before that became an industry norm.
What started as a high-performance cloud testing platform has transformed into an AI-native, multi-agent system powering a connected, end-to-end quality layer. That evolution defined a new identity: LambdaTest evolved into TestMu AI, built for an AI-first future of quality engineering.
Got a question? Email support@testmuai.com or chat with us 24x7 from our chat portal.