LambdaTest Nodejs bindings for Tunnel

Installation

npm i @lambdatest/node-tunnel

Example

1var lambdaTunnel = require('@lambdatest/node-tunnel');
2
3//Creates an instance of Tunnel
4var tunnelInstance = new lambdaTunnel();
5
6// Replace <lambdatest-user> with your user and <lambdatest-accesskey> with your key.
7var tunnelArguments = {
8  user: process.env.LT_USERNAME || '<lambdatest-user>',
9  key: process.env.LT_ACCESS_KEY || '<lambdatest-accesskey>'
10};
11
12// Callback Style
13// Atarts the Tunnel instance with the required arguments
14tunnelInstance.start(tunnelArguments, function(error, status) {
15  if (!error) {
16    console.log('Tunnel is Running Successfully');
17  }
18});
19
20// Promise Style
21tunnelInstance
22  .start(tunnelArguments)
23  .then(status => {
24    console.log('Tunnel is Running Successfully');
25  })
26  .catch(error => {
27    console.log(error);
28  });
29
30// Async/Await Style
31(async function() {
32  try {
33    const istunnelStarted = await tunnelInstance.start(tunnelArguments);
34    console.log('Tunnel is Running Successfully');
35  } catch (error) {
36    console.log(error);
37  }
38})();

Methods

tunnelInstance.start(tunnelArguments, callback)

Start tunnel Instance.

• tunnelArguments: credentials for secure tunnel connection.
  • user: The username for the LambdaTest account.
  • key: The accessKey for the LambdaTest account.
• callback (function(error, status)): A callback to invoke when the API call is complete.

1// Callback Style
2tunnelInstance.start(tunnelArguments, function(error, status) {
3  if (!error) {
4    console.log('Tunnel is Running Successfully');
5  }
6});
7
8// Promise Style
9tunnelInstance
10  .start(tunnelArguments)
11  .then(status => {
12    console.log('Tunnel is Running Successfully');
13  })
14  .catch(error => {
15    console.log(error);
16  });
17
18// Async/Await Style
19(async function() {
20  try {
21    const istunnelStarted = await tunnelInstance.start(tunnelArguments);
22    console.log('Tunnel is Running Successfully');
23  } catch (error) {
24    console.log(error);
25  }
26})();

tunnelInstance.isRunning()

Get Status of tunnel Instance.

1// Callback Style
2tunnelInstance.start(tunnelArguments, function(error, status) {
3  if (!error) {
4    console.log('Tunnel is Running Successfully');
5    var tunnelRunningStatus = tunnelInstance.isRunning();
6    console.log('Tunnel is Running ? ' + tunnelRunningStatus);
7  }
8});
9
10// Promise Style
11tunnelInstance
12  .start(tunnelArguments)
13  .then(status => {
14    console.log('Tunnel is Running Successfully');
15    const tunnelRunningStatus = tunnelInstance.isRunning();
16    console.log('Tunnel is Running ? ' + tunnelRunningStatus);
17  })
18  .catch(error => {
19    console.log(error);
20  });
21
22// Async/Await Style
23(async function() {
24  try {
25    const istunnelStarted = await tunnelInstance.start(tunnelArguments);
26    console.log('Tunnel is Running Successfully');
27    const tunnelRunningStatus = tunnelInstance.isRunning();
28    console.log('Tunnel is Running ? ' + tunnelRunningStatus);
29  } catch (error) {
30    console.log(error);
31  }
32})();

tunnelInstance.getTunnelName(callback)

Get name of the Running tunnel Instance.

• callback (function(tunnelName)): A callback to invoke when the API call is complete.

1// Callback Style
2tunnelInstance.start(tunnelArguments, function(error, status) {
3  if (!error) {
4    console.log('Tunnel is Running Successfully');
5    tunnelInstance.getTunnelName(function(tunnelName) {
6      console.log('Tunnel Name : ' + tunnelName);
7    });
8  }
9});
10
11// Promise Style
12tunnelInstance
13  .start(tunnelArguments)
14  .then(status => {
15    console.log('Tunnel is Running Successfully');
16    tunnelInstance.getTunnelName().then(tunnelName => {
17      console.log('Tunnel Name : ' + tunnelName);
18    });
19  })
20  .catch(error => {
21    console.log(error);
22  });
23
24// Async/Await Style
25(async function() {
26  try {
27    const istunnelStarted = await tunnelInstance.start(tunnelArguments);
28    console.log('Tunnel is Running Successfully');
29    const tunnelName = await tunnelInstance.getTunnelName();
30    console.log('Tunnel Name : ' + tunnelName);
31  } catch (error) {
32    console.log(error);
33  }
34})();

tunnelInstance.stop(callback)

Stop the Running tunnel Instance.

• callback (function(error, status)): A callback to invoke when the API call is complete.

1// Callback Style
2tunnelInstance.start(tunnelArguments, function(error, status) {
3  if (!error) {
4    console.log('Tunnel is Running Successfully');
5    tunnelInstance.stop(function(error, status) {
6      console.log('Tunnel is Stopped ? ' + status);
7    });
8  }
9});
10
11// Promise Style
12tunnelInstance
13  .start(tunnelArguments)
14  .then(status => {
15    console.log('Tunnel is Running Successfully');
16    tunnelInstance.stop().then(status => {
17      console.log('Tunnel is Stopped ? ' + status);
18    });
19  })
20  .catch(error => {
21    console.log(error);
22  });
23
24// Async/Await Style
25(async function() {
26  try {
27    const istunnelStarted = await tunnelInstance.start(tunnelArguments);
28    console.log('Tunnel is Running Successfully');
29    const status = await tunnelInstance.stop();
30    console.log('Tunnel is Stopped ? ' + status);
31  } catch (error) {
32    console.log(error);
33  }
34})();

Arguments

Every modifier except user and key is optional. Visit LambdaTest tunnel modifiers for an entire list of modifiers. Below are demonstration of some modifiers for your reference.

LambdaTest Basic Credentials

Below credentials will be used to perform basic authentication of your LambdaTest account.

• user (Username of your LambdaTest account)
• key (Access Key of your LambdaTest account)

Port

If you wish to connect tunnel on a specific port.

• port : (optional) Local port to connect tunnel.

1tunnelArguments = {
2  user: process.env.LT_USERNAME || '<lambdatest-user>',
3  key: process.env.LT_ACCESS_KEY || '<lambdatest-accesskey>',
4  port: '<port>'
5};

Proxy

If you wish to perform tunnel testing using a proxy.

• proxyhost: Hostname/IP of proxy, this is a mandatory value.
• proxyport: Port for the proxy, by default it would consider 3128 if proxyhost is used For Basic Authentication, we use the below proxy options:
• proxyuser: Username for connecting to proxy, mandatory value for using 'proxypass'
• proxypass: Password for the USERNAME option.

1tunnelArguments = {
2  user: process.env.LT_USERNAME || '<lambdatest-user>',
3  key: process.env.LT_ACCESS_KEY || '<lambdatest-accesskey>',
4  proxyHost: '127.0.0.1',
5  proxyPort: '8000',
6  proxyUser: 'user',
7  proxyPass: 'password'
8};

Tunnel Name

Human readable tunnel identifier

• tunnelName: (Name of the tunnel)

1tunnelArguments = {
2  user: process.env.LT_USERNAME || '<lambdatest-user>',
3  key: process.env.LT_ACCESS_KEY || '<lambdatest-accesskey>',
4  tunnelName: '<your-tunnel-name>'
5};

Testing Local Folder

Populate the path of the local folder you want to test in your internal server as a value in the below modifier.

• dir/localdir/localdirectory : Path of the local folder you want to test

1tunnelArguments = {
2  user: process.env.LT_USERNAME || '<lambdatest-user>',
3  key: process.env.LT_ACCESS_KEY || '<lambdatest-accesskey>',
4  dir: '<path of the local folder you want to test>'
5};

Enable Verbose Logging

To log every request to stdout.

• v/verbose : true or false

1tunnelArguments = {
2  user: process.env.LT_USERNAME || '<lambdatest-user>',
3  key: process.env.LT_ACCESS_KEY || '<lambdatest-accesskey>',
4  v: true
5};

Additional Arguments

Logfile You can provide a specific path to this file. If you won't provide a path then the logs would be saved in your present working directory by the filename: tunnel.log. For providing a specific path use the below argument:

• logFile : path

1tunnelArguments = {
2  user: process.env.LT_USERNAME || '<lambdatest-user>',
3  key: process.env.LT_ACCESS_KEY || '<lambdatest-accesskey>',
4  logFile: '/lambdatest/logs.txt'
5};

• egressOnly: Uses proxy settings only for outbound requests.
• ingressOnly: Uses proxy settings only for inbound requests.
• dns: Comma separated list of dns servers
• sshConnType: Specify type of ssh connection (over_22, over_443, over_ws)
• mode: Specifies in which mode tunnel should run [ssh,ws]
• nows: Force tunnel to run in non websocket mode
• mitm: MITM mode, used for testing websites with private certificates

Contribute

Reporting bugs

Our GitHub Issue Tracker will help you log bug reports.

Tips for submitting an issue: Keep in mind, you don't end up submitting two issues with the same information. Make sure you add a unique input in every issue that you submit. You could also provide a "+1" value in the comments.

Always provide the steps to reproduce before you submit a bug. Provide the environment details where you received the issue i.e. Browser Name, Browser Version, Operating System, Screen Resolution and more. Describe the situation that led to your encounter with bug. Describe the expected output, and the actual output precisely.

Pull Requests

We don't want to pull breaks in case you want to customize your LambdaTest experience. Before you proceed with implementing pull requests, keep in mind the following. Make sure you stick to coding conventions. Once you include tests, ensure that they all pass. Make sure to clean up your Git history, prior your submission of a pull-request. You can do so by using the interactive rebase command for committing and squashing, simultaneously with minor changes + fixes into the corresponding commits.

About LambdaTest

LambdaTest is a cloud based selenium grid infrastructure that can help you run automated cross browser compatibility tests on 2000+ different browser and operating system environments. LambdaTest supports all programming languages and frameworks that are supported with Selenium, and have easy integrations with all popular CI/CD platforms. It's a perfect solution to bring your selenium automation testing to cloud based infrastructure that not only helps you increase your test coverage over multiple desktop and mobile browsers, but also allows you to cut down your test execution time by running tests on parallel.