Do I need to install the TestMu AI Tunnel binary manually?

No. The GitHub Action downloads the tunnel binary on the runner, authenticates with your stored secrets, keeps the connection alive while your tests run, and shuts it down automatically when the job finishes.

How do my tests route through the tunnel?

Set tunnel: true and the same tunnelName from your workflow in the test capabilities, and the grid routes those browser sessions through the tunnel to your local build. Capability examples per framework are in the local testing documentation.

Can you use GitHub Actions for free?

Yes. GitHub Actions is free for public repositories on GitHub-hosted standard runners, and private repositories on the GitHub Free plan include 2,000 Actions minutes per month. The TestMu AI free plan includes tunnel access, so you can try this workflow end to end without a paid plan.

Why is the action still named LambdaTest-tunnel-action?

LambdaTest rebranded to TestMu AI, and the action keeps its original GitHub namespace so existing workflows never break: reference LambdaTest/LambdaTest-tunnel-action@v2. Your LT_USERNAME and LT_ACCESS_KEY secrets and tunnel configuration keep working unchanged.

Can my whole team share one tunnel?

Yes. Pass sharedTunnel under the action's with: block to share a single tunnel across everyone in your organization, instead of starting a separate tunnel for every parallel job or teammate.

How do I debug a tunnel that cannot reach my local server?

Enable the verbose input for detailed tunnel logging and archive the log with the action's logFileName output, as the workflow on this page does with upload-artifact. The log shows whether the tunnel connected, which requests it received, and where resolution failed.

GitHub Actions For TestMu AI Tunnel: Setup Guide

Start the TestMu AI Tunnel inside your GitHub Actions workflow with one YAML block and test locally or privately hosted builds on 10,000+ browsers and real devices.

Start free with Google

Start free with Email

World’s largest virtual agentic engineering & quality conference

WHENAUG 19-21

WHEREVirtual · Global

Trusted by 3M+ users globally at

+Read case study

Copy-Paste the main.yml Tunnel Workflow

On every push and pull request: check out code, start the TestMu AI Tunnel with the v2 action, run tests, and archive tunnel logs.

Full setup steps and per-framework capabilities live in the local testing guide. Check out our documentation

Copied to Clipboard!

Three Steps to Local Testing in CI

Add your secrets once, commit one workflow block, and tune the tunnel for proxies, teams, and debugging.

Start free with Google

PREREQUISITES

Set Up GitHub Secrets

The tunnel action authenticates with the username and access key from your TestMu AI dashboard. Store both as encrypted repository secrets before you edit main.yml.

Get Your Access Key

Copy your username and access key from Password & Security
Create LT_USERNAME and LT_ACCESS_KEY under Settings > Secrets and variables > Actions
Reference them as secrets in the workflow, never in plain text

WORKFLOW

Add the Workflow Block

The main.yml example above checks out your code, starts the tunnel with the v2 action, runs your suite against the grid, and tears everything down when the job ends.

Run It Free

Check out code with actions/checkout on ubuntu-latest
Start the tunnel step with your stored secrets
Set tunnel: true and your tunnelName in test capabilities

TUNNEL CONFIGURATION

Configure the Tunnel

Only user, accessKey, and tunnelName are required. Optional inputs handle proxies, shared tunnels, DNS overrides, and verbose logging for restricted networks.

Read the Tunnel Docs

Route through corporate proxies with proxyHost and proxyPort
Share one tunnel across the team with sharedTunnel
Debug CI runs with verbose logs and the logFileName output

Tunnel Action Inputs and Outputs

Start free with Google

Everything the action accepts under with:, plus the outputs port, logFileName, and usePrivateIP for later workflow steps.

Required

What it does

user

Yes

Your TestMu AI username, via LT_USERNAME

accessKey

Yes

Your TestMu AI access key, via LT_ACCESS_KEY

tunnelName

Yes

Unique name matched by tunnelName in test capabilities

proxyHost / proxyPort

Route the tunnel through a corporate proxy

proxyUser / proxyPass

Credentials when the proxy requires authentication

sharedTunnel

Share one tunnel across your whole organization

dns

Comma-separated list of custom DNS servers

bypassHosts

Hosts that resolve publicly and skip the tunnel

basicAuth

Credentials for staging environments behind basic auth

verbose

Detailed tunnel logging, exported via the logFileName output

Success Stories of TestMu AI (Formerly LambdaTest)

50%

reduction in test execution time

“HyperExecute is a highly reliable test execution platform and has excellent customer support.”

Sagar Uday Kumar

Sr. Engineering Manager

Some Love from our Customers

As Best Egg expanded its product offerings and entered new markets, we knew our old testing infrastructure couldn’t keep up.
With support from Tenny Agustin, our Engineering Operations Lead, we modernized our approach with

TestMu AI

Best Egg

best-egg

Excited to Share My Learning Journey with Kane AI & Lambda Tool!
I'm pleased to announce that I've recently gained hands-on experience exploring Kane AI through the Lambda Tool and it’s been a fantastic journey of upskilling!

KaneAI

Suryateja Goud

suryateja-goud

See how is #Futureready to enable blazing-fast test orchestration seamlessly integrated with organizations' existing CI/CD platforms, using #Microsoft Azure.

TestMu AI

Microsoft India

MicrosoftIndia

View all reviews

More Reasons to LoveTestMu AI (formerly LambdaTest)

See how TestMu AI speeds up your testing with AI-native authoring, faster execution, and deeper test insights across web, mobile, and AI applications.

Start free with Google