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.

Does the LambdaTest tunnel action still work after the TestMu AI rebrand?

Yes. LambdaTest rebranded to TestMu AI, and the action keeps its original namespace: reference LambdaTest/LambdaTest-tunnel-action@v2 in your workflow. Your existing LT_USERNAME and LT_ACCESS_KEY secrets and tunnel configuration keep working unchanged.

How do my tests know to use 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.

Do I need to download the tunnel binary myself?

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.

Can my team share one tunnel instead of one per job?

Yes. Pass sharedTunnel under the action's with: block to share a single tunnel across everyone in your organization. That avoids spinning up a separate tunnel for every parallel job or teammate.

How do I debug when the workflow cannot reach my local app?

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.

LambdaTest Tunnel GitHub Actions: Setup Guide

LambdaTest is now TestMu AI. Add one block to your GitHub Actions workflow and test locally or privately hosted builds on 10,000+ browsers and real devices.

Start free with Google

Start free with Email

Automate Browser Flows from your
Terminal with Kane CLI

Explore Kane CLI

Trusted by 2M+ users globally at

+Read case study

Copy-Paste Workflow: Start the Tunnel in main.yml

Runs on every push and pull request: check out code, start the 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!

Set Up the Tunnel Action in Three Steps

Store credentials as encrypted secrets, drop one block into main.yml, and tune the tunnel for your network.

Start free with Google

PREREQUISITES

Add Your GitHub Secrets

The action authenticates with your TestMu AI username and access key. Store both as encrypted repository secrets so they never appear in logs or forks.

Get Your Access Key

Copy your username and access key from Password & Security
Add LT_USERNAME and LT_ACCESS_KEY under Settings > Secrets and variables > Actions
Reference them as secrets in main.yml, never in plain text

WORKFLOW

Configure main.yml

One block in .github/workflows/main.yml 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 LambdaTest/LambdaTest-tunnel-action@v2 with your secrets
Set tunnel: true and your tunnelName in test capabilities

TUNNEL CONFIGURATION

Tune Tunnel Inputs

Only user, accessKey, and tunnelName are required. Optional inputs cover proxies, shared tunnels, custom DNS, and verbose logs 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

Every Tunnel Input at a Glance

Start free with Google

All inputs the action accepts under with:, plus the log output you can reference from 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