LambdaTestAutomation Testing ● GitLab CI Integration with LambdaTest

GitLab CI Integration with LambdaTest

GitLab is one of the finest tools which facilitates continuous integration for GitHub projects from small to enterprise level clients. Now, deploy your code rapidly and test it thoroughly for a robust delivery in your go-to-market launch.

LambdaTest now integrates with GitLab CI to boost your go-to-market delivery. Perform automated cross browser testing with LambdaTest to ensure your development code renders seamlessly through an online Selenium grid providing 2000+ real browsers running through machines, on our cloud servers. Perform automation testing in parallel with LambdaTest’s Selenium grid to drastically trim down your test cycles.

This topic will demonstrate how you can leverage LambdaTest Integration with GitLab CI. We will be running our automation script using the Protractor framework.

Prerequisites For Integrating GitLab CI With Our Online Selenium Grid

In order to perform your protractor tests with LambdaTest, you would need the below things to be already set up.

  1. Global Dependencies
    • A Git or GitHub repository.
    • Download and install node.js and node package manager or npm.
    • To install node.js with homebrew use the command below
    • If you have npm already installed, you may want to upgrade it to latest version. Here the code you can run in your terminal to upgrade npm.
    • Upgrade npm to latest version using the below command.
    • Install protractor using npm with the below command.

  2. LambdaTest Authentication Credential
  3. Be aware of your LambdaTest authentication credentials i.e. your LambdaTest username, access key and HubURL. You need to set them up as your environment variables. You can retrieve them from your LambdaTest automation dashboard by clicking on the key icon near the help button.

    • For Linux/Mac
    • For Windows

Integrating LambdaTest With GitLab CI

To integrate GitLab CI with LambdaTest you need to make minor tweaks in the .gitlab-ci.yml which is the configuration file for your GitLab CI instance. The changes you need to make will revolve around the environment variables such as access key, username, grid config and so on.

Below is a sample config file for integrating GitLab CI with LambdaTest. You can use the sample file to test your own automation test suite by replacing the environment variables according to your need. All the code used for the demonstration of this topic can be find in our GitHub repository.

LambdaTest offers a Selenium Desired Capabilities Generator to fetch coded values for your desired test configurations. For Instance, if you select the below configurations:

Selected Values
Operating System
Windows 8.1
Mozilla Firefox
Browser Version
Selenium Version

Then Capabilities Generator at LambdaTest will provide you with the below program:

For more information, refer to our documentation on Selenium Automation Capabilities.

Testing Locally Hosted or Privately Hosted Projects

To help you perform cross browser testing of your locally stored web pages, LambdaTest provides an SSH(Secure Shell) tunnel connection with the name LambdaTest Tunnel. With LambdaTest Tunnel, you can execute a test server inside your GitLab CI build a container to perform automated cross browser testing on browsers offered by Selenium grid on LambdaTest. So you make sure how well your changes look, even before your customers.
Curious to know more about LambdaTest Tunnel?

Follow our documentation on LambdaTest Tunnel to know it all. OS specific instructions to download and setup tunnel binary can be found at the following links.

The below example of .gitlab-ci.yml file would demonstrate you on how to leverage LambdaTest’s Selenium grid by performing a browser test through your testing server contained in your GitLab CI build.

Once, the tunnel is successfully set up. You can add the below code to your capabilities for testing internal servers on your network.

Parallel Testing

Parallel Testing is one of the most demanding features of LambdaTest Selenium Grid. By parallel testing, you can run more than one test case, simultaneously. This means that Parallel testing would allow you to execute numerous automation test cases altogether. So you execute a single test scenario across different browsers or could run different test scenarios across the same browser but with different browser versions.

To perform automation testing in parallel on Windows use the below command.

Monitor and analyze your test result on the LambdaTest Automation Dashboard.

Deploy your code in a reliable manner at scale using GitLab CI integration with LambdaTest, and ensure it looks robust across every browser to provide a seamless user experience to all your visitors. Happy Testing!