Integrate LambdaTest Extension With Azure Pipelines


Azure Pipelines, by Microsoft, is a feature of Azure DevOps. It helps to automatically build, test, and deploy your projects, with Continous Integration or CI, upon various production environments. So your Selenium automation test scripts can run successfully on Azure Pipeline. However, sometimes running your scripts can be a bit tedious. This is where the LambdaTest plugin can be used in the Azure Pipeline to ease the workflow and automate the tests. LambdaTest allows you to perform live interactive and automated cross-browser testing on 2000+ real browsers and operating systems online.

Benefits Of Using LambdaTest Plugin In Azure Pipeline


  • Setup your LambdaTest account in Azure Pipeline using your account credentials.
  • Set up, and use the Lambda Tunnel for testing various production environments like internal, development and staging.
  • Embed or fetch LambdaTest test results in your project’s job results.
  • Witness the execution of the tests, capture screenshots, mark bugs, plot graph and much more, on your automation dashboard on LambdaTest.

Prerequisites


  • Azure DevOps (Azure Pipelines) account
  • LambdaTest account credentials.
    1. LambdaTest Username
    2. LambdaTest Access Key

    You can fetch your account credentials on LambdaTest from your profile section.

How To Install Lambdatest Extension


Follow the below steps to install Lambdatest Extension from Azure DevOps marketplace:

  1. Go to Azure DevOps marketplace and search for “LambdaTest” in the search box.

  2. In the results window, you will see an option showing the LambdaTest Extension.

  3. Open the found result and click on “Get it free”, to get the LambdaTest Extension in your organization for free.

  4. Select an Azure DevOps organization and press “Install”. LambdaTest Extension will be installed in this organization.

  5. Once finished, you can see “Done” at the top. It means that LambdaTest Extension has been installed successfully. You can proceed to your organization to see the extension.

How To Integrate LambdaTest Plugin In Azure Pipelines


Step 1: Sign in to your Azure DevOps account to access the Azure Pipelines. Create one if you don’t have any.

Step 2: Create a project and download the LambdaTest extension from the Azure marketplace as shown above.

Step 3: In order to use the LambdaTest extension now, select Pipelines from the left side menu bar as shown below:

Step 4: Select New Pipelines from the top right corner of your screen.

Step 5: Switch to Class Editor from the footer.

Step 6: Select your choice of versioning control software you use, from the given options. For this demo, we have used “Github”.

Step 7: Select the template as Empty Job to begin with. We will create the job as we go.

Step 8: Add a new task in the job with the help of + button, and fill the required details.

For this demo purpose, we have used following tasks:

  • Search “LambdaTest” in the search menu, and select LambdaTest Configuration Setup and Lambda Stop Tunnel from the available tasks.
  • Similarly, add Command Line Script and Python Script in to this job.
  • Once added, arrange the tasks in below shown order:

Step 9: Click on LambdaTest Configuration Setup and then click on New.

Step 10: Fill the required details. For this demo purpose, we have used following details:

  • Select Basic Authentication mode of integration from the given authentication methods.
  • Enter your LambdaTest username as “Username” and LambdaTest Access Key as “Password” and then click on verify button.
  • Enter the desired Service connection name in the Details section and then click Verify and Save button.

  • You can also activate the Lambda Tunnel for localhost testing. Just select Service connection from the drop down list and Select Lambda Tunnel.

Step 11: Now we need to install Selenium in our job to perform the automation tests. Click on Command Line Script and enter the following commands to install Selenium:

Step 12: Select Run a Python script as we have selected Python in the above steps.

Select your script to execute either from your repository using the “File Path” option, or you can also write the script inline using the “Inline” option. Once the script is ready, click on “OK”

Step 13: Now we have imported everything to run our tests. Click on “Save & Queue” to run your test.

Step 14: Select OS from Agent Specification as shown below and click “Save and Run”.

Step 15: The pipeline will get activated and you can see your job queued to be executed.

Select your job from the Jobs section, as shown above, to see the output of your tests.

Step 16: You can view your tasks getting executed and their logs, by clicking on the job which you have queued for execution. Once the test passes/fails, the status of the pipeline will be updated accordingly.

How To Find Test Execution Results On LambdaTest


The output of the tests executed above can be seen in your authenticated LambdaTest account as well. Follow the below steps to see your test execution result:

Step 1: Login into your LambdaTest account using the credentials used above in the Azure Pipelines.

Step 2: Go to “Automations” tab from your left menu.

Step 3: Here you can see the executed tests along with their builds, details and status, as shown below:

Not only this, but you can also use this automation dashboard to obtain Test logs, Analytics, Mark Bugs, Integrate apps from our diverse app store, fetch build details, and much more. LambdaTest Selenium Automation Grid enables you to perform end-to-end automation tests on a secure, reliable, and scalable Selenium infrastructure. You can perform automated cross-browser testing with Selenium scripts on 2000+ browsers and operating systems environments giving you higher test coverage and at significantly less built times. LambdaTest will help you evaluate how well your web application renders when accessed through a variety of different browsers. You can perform automated cross-browser testing of your locally hosted web pages using Lambda Tunnel. You could also run a single test across multiple browser/OS configurations, simultaneously.

That was all you need to know for integrating LambdaTest Extenstion with Azure Pipelines. Increase your productivity with our integrations. If you still have any questions for us, please feel free to let us know. Our experts are always available on chat to help you out with any roadblock regarding our product. Happy testing! 🙂

Integrating Wrike With LambdaTest


Wrike is a SaaS(Software-As-A-Service) Product Management software. You can manage and track your projects, deadlines, and other workflow processes. It also allows inter-team communications, and therefore used by many developments, as well as testing teams to keep track of their work and teams. Wrike also provides the ability to track bugs effectively.

LambdaTest Wrike integration helps you in creating issues in Wrike directly from the LambdaTest platform. LambdaTest now allows you to integrate your Wrike workspace with simple one-click. You can push annotated issues to a project of your choice, assign it to the required teammate, set the priority, and attach screenshots in the middle of the test session. After creating the issue, it gets reflected directly in your project’s workspace on Wrike with the details of the test session along with the annotated screenshot.

Wrike Integration with LambdaTest, like all of the integrations to 3rd party applications, is available for freemium as well as premium plan.

Integrate Wrike With Your LambdaTest Account


Step 1: Login to your LambdaTest account. You need to have an Admin or User level access to see and install 3rd party integrations.

Step 2: Select ‘Integrations’ tab from the left navigation menu bar. This will guide you to a screen where you will find a list of 3rd party applications, that have already been integrated as well as that are available to integrate with your LambdaTest account.

Step 3: Hover to the ‘Wrike’ block under “Project Management” category, and click on “Add” button that appears.

Step 4: You need to create an account on Wrike to integrate your workspace with LambdaTest. If you don’t have an account, you can create one even in the middle of this integration in the this step. If you are already logged in, this step won’t appear in the integration process.

Step 5: Review the privacy policy and click on “Accept”.

Step 6: Once you press on “Accept”, Wrike will be integrated with LambdaTest on the same account, and an alert-box will appear on the top right corner of the screen stating that the integration is successfull.

Step 7: Congrats! Wrike has been successfully integrated. Go to Integrations tab again and you will see Wrike under the “My Integrations” tab.

Also, you can see a green tick in front of Wrike under Project Management category, indicating that Wrike has been successfully installed.

How To Log Your First Bug Through Wrike Integration?


Step 1: Select any of the test from the left navigation menu of LambdaTest. For this instance, we will be taking “Real Time Testing” option.

Step 2: Enter the URL of the web-app to be tested in the URL box. Press ‘Start’ after selecting the configuration of browser and operating system as per your choice.

Step 3: After the VM is launched and operable, you can perform testing on your web-app as per your choice, such as for finding issues. Suppose if you come across any bug, then you need to click on the Bug icon from the left panel, for capturing a screenshot of the current VM instance.

Step 4: A screenshot will be captured and appear on your screen in an in-built image editor. Annotate any issue as per your choice in this editor, and then press “Mark as Bug” button.

Step 5: Complete the Bug/Task/Issue Form that appears upon clicking the “Mark as Bug” button, as per your requirement:

  • Select the Folder from your Wrike workspace, in which you want to create this issue.
  • You can assign the bug to a member of your team or yourself, by selecting from the drop-down of field ‘Assignee‘.
  • Set the Priority of the bug as per convenience.
  • Give a title to your bug in the “Title” field.
  • Also, post an optional description to help the assignee with the bug tracking.

Now click on “Create Bug” button create the bug and send the bug directly to selected project.

Step 6: After you click on “Create Bug”, you will be able to observe it being successfully marked through a single click effort. You will get prompt messages on top of your Virtual Machine indicating the progress of bug logging. After few seconds you will be notified with a prompt message “Bug successfully marked” indicating that the screenshot has been pushed to your Wrike workspace.

Step 7: Login to your workspace on Wrike and you will be able to notice the marked bug in the set channel assigned to the selected person. All the data you provided through Lambdatest form would already be presented in it. LambdaTest automatically includes test environment details and related screenshots in the screenshot as attachments.

A clickable link will be provided in the Wrike channel along with the screenshot to instantly route users on their browser for a full screen view of the bug.

How To Remove Wrike Integration?


You can work with one integration at a time. So if you would want to integrate to a similar 3rd party application, then you would have to remove your current integration. Here is how you can do that.

Step 1: Login to your LambdaTest account.

Step 2: Select ‘Integrations’ from the left navigation menu bar & go to ‘Product Management’ category. This will guide you to a screen where you will find 3rd party applications, available to integrate with your LambdaTest account. You can also remove it using the ‘My Integrations’ tab on the Integrations tab.

Step 3: On the Wrike block. A “REMOVE” button will appear. Click on ‘REMOVE’.

Step 4: Upon pressing ‘REMOVE’, a message will prompt on the top right corner of the app stating the same.

That was all you need to know for LambdaTest + Wrike Integration. Increase your productivity multifold with our integrations. If you still have any questions for us, please feel free to let us know. Our experts are always available on chat to help you out with any roadblock regarding our product. Happy testing!

Integrating Mattermost With LambdaTest


Mattermost is a Communication platform, written in Golang and React, and is open-source, self-hostable, easy to deploy, manage, and upgrade. It is a secure workplace which allows messaging from behind your firewall. Mattermost is a famous alternative to proprietary SaaS messaging apps, as it allows you to bring all your team communication into a single place, making it anywhere searchable and accessible.

The LambdaTest Mattermost Integration allows you to share or push a bug to your specified Mattermost channel from the LambdaTest platform in a single click. You can share any UI observations and input with your team on Mattermost anytime, by just capturing a screenshot in the middle of your test session through LambdaTest. You can also annotate the screenshot or highlight your issue or input. The fields populated by you while marking as a bug through LambdaTest gets displayed as information on Mattermost for that testing instance.

Mattermost Integration with LambdaTest, like all of the integrations to 3rd party applications, is available for freemium as well as premium plan.

Integrate Mattermost With Your LambdaTest Account


Step 1: Login to your LambdaTest account. Make sure you have an Admin or User level access to see and install 3rd party integrations.

Step 2: Select ‘Integrations’ tab from the left navigation menu bar. This will guide you to a screen where you will find a list of 3rd party applications, that have already been integrated as well as that are available to integrate with your LambdaTest account.

Step 3: Hover to the ‘Mattermost’ block under “Communications” category, and click on “Add” button that appears.

Step 4: You need a webhook URL to integrate your workspace with LambdaTest. So copy the webhook URL of the proposed LambdaTest integration on Mattermost.

In case you don’t have a webhook ready, you can find read about how to create a webhook here.

Step 5: Enter your webhook URL copied from the above step, in the box that appears after clicking on Add in step 3, and then press “Install

Step 6: Once you press on Install, Mattermost will be integrated with LambdaTest on the same webhook URL, and an alert-box will appear on the top right corner of the screen stating that the integration is successfull.

Step 7: Voila! Go to Integrations tab again and you will see a Mattermost under “My Integrations”.

Also, you can see a green tick in front of Mattermost under Communication category, indicating that Mattermost has been successfully installed.

How To Log Your First Bug Through Mattermost Integration?


Step 1: Select any of the test from the left navigation menu of LambdaTest. For this instance, we will be taking “Real Time Testing” option.

Step 2: Enter the URL of the web-app to be tested in the URL box. Press ‘Start’ after selecting the configuration of browser and operating system as per your choice.

Step 3: After the VM is launched and operable, you can perform testing on your web-app as per your choice, such as for finding bugs. Suppose if you come across any bug, then you need to click on the Bug icon from the left panel, for capturing a screenshot of the current VM instance.

Step 4: A screenshot will be captured and appear on your screen in an in-built image editor. Annotate any issue or a task as per your choice in this editor, and then press “Mark as Bug” button.

Step 5: Complete the Bug/Task/Issue Form that appears upon clicking the “Mark as Bug” button, as per your requirement:

  • Select the Issue type as Bug/Task/Issue. Here, we have selected it as Bug.
  • Set the Priority of the bug as per convinience.
  • You can assign the bug to a member of your team by populating the field ‘Assignee‘.
  • Write the ‘Summary‘ of the bug that would be sent to the assigned member.
  • You also get to post an optional description to help with the bug.

At the bottom of the form, please make sure to tick the check button
stating “Send to Mattermost”.

Note: By default, it would be checked, if Mattermost is already integrated. This button helps send the screenshot, as per the filled form, directly to your workspace, when the Bug is created. You can uncheck the button anytime if you do not wish the bug/task/issue on Mattermost

Now click on “Create Bug” button to send the bug directly to Mattermost workspace.

Step 6: After you click on “Create Bug”, you will be able to observe it being successfully marked through a single click effort. You will get prompt messages on top of your Virtual Machine indicating the progress of bug logging. After few seconds you will be notified with a prompt message “Bug successfully marked” indicating that the screenshot has been pushed to your Mattermost workspace.

Login to your workspace on Mattermost and you will be able to notice the marked bug in the set channel assigned to the set person. All the data you provided through Lambdatest form would already be presented in it. LambdaTest automatically includes test environment details and related screenshots in the screenshot as attachments.

A clickable link will be provided in the Mattermost channel along with the screenshot to instantly route users on their browser for a full screen view of the bug.

How To Remove Mattermost Integration?


You can work with one integration at a time. So if you would want to integrate to a similar 3rd party application, then you would have to remove your current integration. Here is how you can do that.

Step 1: Login to your LambdaTest account.

Step 2: Select ‘Integrations’ from the left navigation menu bar & go to ‘Communications’ category. This will guide you to a screen where you will find 3rd party applications, available to integrate with your LambdaTest account.

Step 3: Hover to Mattermost block. A “REMOVE” button will appear. Click on ‘REMOVE’.

That was all you need to know for LambdaTest + Mattermost Integration. Increase your productivity multifold with our integrations. If you still have any questions for us, please feel free to let us know. Our experts are always available on chat to help you out with any roadblock regarding our product. Happy testing!

Run Selenium IDE Tests With LambdaTest Selenium Grid On Cloud

Selenium IDE is one of the most popular record and playback tool for testing which is widely used for automated browser testing. The Selenium IDE is a very easy-to-use solution for getting started with automation testing. It also provides instant feedback and has cross-browser and operating system compatibility, with the help of Selenium IDE (SIDE) Runner.

In this article, we will see how to run Selenium IDE tests on LambdaTest Selenium Cloud Grid.

Prerequisites


  • Node.js programming language (version 8 or 10).
  • NPM or Node.js Package Manager.
  • Selenium IDE Plugin, for either Google Chrome and Mozilla Firefox.
  • Selenium IDE (SIDE) Runner. You can download SIDE runner using below code:
  • You also need your LambdaTest authentication credentials, which includes your LambdaTest username, and access key. These will be set up as the Secrets for configuring the pipeline. To get your Username and Access Key, go to your LambdaTest automation dashboard and click on the “key” icon left to the help button, on the top right corner.

For the demonstration of executing Selenium IDE tests on the LambdaTest grid, we’ll create a test suite that comprises of four test cases- two to perform a search for ‘LambdaTest’ on Google & DuckDuckGo, and the other two to perform a search for ‘LambdaTest Blog’ on Google & DuckDuckGo.

Enabling Parallel Testing for Selenium IDE


The parallel testing on the Cloud Selenium Grid works only when the tests are executed using the SIDE Runner, and not the Selenium IDE. So we will enable the Parallel testing for Selenium IDE.

  • Right click on the test suite and go to Settings.
  • In the Settings window, tick the Run in Parallel checkbox.
  • Save the SIDE project.

We have successfully activated Parallel Testing in Selenium IDE. Now we can execute tests Selenium IDE tests in parallel on LambdaTest Selenium Cloud Grid.

Executing Selenium IDE Tests on LambdaTest Selenium Cloud Grid


  1. Set the Desired Capabilities in Selenium. For this article, we have set the Chrome browser (version 72.0) for Windows 10, to run our Selenium IDE tests.

    The LambdaTest Selenium Desired Capabilities Generator is used to generate the capabilities. Below are the desired capabilities used in this article for the required test combination, provided in Python Language.

    In the string format, it will be represented as:

  2. Get the Grid URL for executing tests on LambdaTest. Get your username and access key from your LambdaTest’s Profile section (as shown in the prerequisites), and replace it in the below URL.
  3. Specify the desired capabilities along with the Grid URL. Replace the desired capabilities and the Grid URL from the above steps in the below code:
  4. Mention the number of parallel processes to be executed at a time. You can use any of the below syntax to specify the count of parallel processes to be executed at the above mentioned Grid URL:

    OR

    For this article, we have set the number of parallel processes as ‘4’

  5. Now we have all the components of the SIDE Runner command to execute the tests. So we will run the Selenium IDE tests on LambdaTest Selenium Cloud Grid. Navigate to the directory where the .SIDE file is located (here it is located at “LambdaTest-IDE.side“) and excecute the below command in the terminal, after replacing the GRID URL:

We have successfully executed all the steps to run Selenium IDE tests on LambdaTest Selenium Cloud Grid. Now you can see our tests being executed along with their status in the Automation Timeline of your LambdaTest profile.

Below are the execution snapshots of the SIDE Runner and the automation timeline instance, that shows the successful execution of the desired tests:

How To Run Multiple Test Cases Within Same Test Suite?


You might have lots of individual tests in a single test suite to test all features of a site. When you run these tests normally, you might experience that the test suites get broken into individual tests, thereby requiring a new session and the variables being passed again each time.

Selenium IDE provides the feature to overcome this as well. In order to run multiple test cases within the same test suite with a single instance of a browser, the Persist session option in the Selenium IDE can be used. Below are the steps for how to do so:

  1. Click over the three dot option of the test suite. Choose the setting option.
  2. Then choose persist session option and submit.

  3. For the second query, you pass the variable value through the SIDE Runner using command line. You can use the SIDE Runner’s “param” flag to pass the values.
    For example:

Congrats! We have successfully executed our Selenium IDE tests on LambdaTest Selenium Cloud Grid, which allows you to perform live interactive and automated cross-browser testing on 2000+ real browsers and operating systems online.

Rocket.Chat Integration With LambdaTest


Rocket.Chat is a Communication platform, which is free, open-source, scalable, highly customizable, and secure. It not only allows you to communicate and collaborate with your team, but also share files and live chat in real time. It is a cross-platform, which means it can run on different types of operating systems like Linux, Windows, macOS, Android, and iOS. The biggest advantage of using Rocket.Chat is that it allows you to access its source code, since it is open source. Therefore, you can fully customize, extend, or add new functionality to it to meet your team’s or business requirements.

The LambdaTest Rocket.Chat Integration allows you to share or push a bug to your specified Rocket.Chat channel from the LambdaTest platform in a single click. You can share any UI observations and input with your team on Rocket.Chat anytime, by just capturing a screenshot in the middle of your test session through LambdaTest. You can also annotate the screenshot or highlight your issue or input. The fields populated by you while marking as bug through LambdaTest gets displayed as information on Rocket.Chat for that testing instance.

Rocket.Chat Integration with LambdaTest, like all of the integrations to 3rd party applications, is available for freemium as well as premium plan.

Integrate Rocket.Chat With Your LambdaTest Account


Step 1: Login to your LambdaTest account. Make sure you have an Admin or User level access to see and install 3rd party integrations.

Step 2: Select ‘Integrations’ tab from the left navigation menu bar. This will guide you to a screen where you will find a list of 3rd party applications, that have already been integrated as well as that are available to integrate with your LambdaTest account.

Step 3: Hover to the ‘Rocket.Chat’ block under “Communications” category, and click on “Add” button that appears.

Step 4: You need a webhook URL to integrate your workspace with LambdaTest. So copy the webhook URL of the proposed LambdaTest integration on Rocket.Chat.

In case you don’t have a webhook ready, you can find read about how to create a webhook here.

Make sure to mark the creating integration as “Enabled” on Rocket.Chat.

Step 5: Enter your webhook URL copied from the above step, in the box that appears after clicking on Add in step 3, and then press “Install

Step 6: Once you press on Install, Rocket.Chat will be integrated with LambdaTest on the same webhook URL, and an alert-box will appear on the top right corner of the screen stating that the integration is successfull.

Step 7: Voila! Go to Integrations tab again and you will see a Rocket.Chat under “My Integrations”.

Also, you can see a green tick in front of Rocket.Chat under Communication category, indicating that Rocket.Chat has been successfully installed.

How To Log Your First Bug Through Rocket.Chat Integration?


Step 1: Select any of the test from the left navigation menu of LambdaTest. For this instance, we will be taking “Real Time Test” option.

Step 2: Enter the URL of the web-app to be tested in the URL box. Press ‘Start’ after selecting the configuration of browser and operating system as per your choice.

Step 3: After the VM is launched and operable, you can perform testing on your web-app as per your choice, such as for finding bugs. Suppose if you come across any bug, then you need to click on the Bug icon from the left panel, for capturing a screenshot of the current VM instance.

Step 4: A screenshot will be captured and appear on your screen in an in-built image editor. Annotate any issue or a task as per your choice in this editor, and then press “Mark as Bug” button.

Step 5: Complete the Bug/Task/Issue Form that appears upon clicking the “Mark as Bug” button, as per your requirement:

  • Select the Issue type as Bug/Task/Issue. Here, we have selected it as Bug.
  • Set the Priority of the bug as per convinience.
  • You can assign the bug to a member of your team by populating the field ‘Assignee‘.
  • Write the ‘Summary‘ of the bug that would be sent to the assigned member.
  • You also get to post an optional description to help with the bug.

At the bottom of the form, please make sure to tick the check button
stating “Send to Rocket.Chat”.

Note: By default, it would be checked, if Rocket.Chat is already integrated. This button helps send the screenshot, as per the filled form, directly to your workspace, when the Bug is created. You can uncheck the button anytime if you do not wish the bug/task/issue on Rocket.Chat

Now click on “Create Bug” button to send the bug directly to Rocket.Chat workspace.

Step 6: After you click on “Create Bug”, you will be able to observe it being successfully marked through a single click effort. You will get prompt messages on top of your Virtual Machine indicating the progress of bug logging. After few seconds you will be notified with a prompt message “Bug successfully marked” indicating that the screenshot has been pushed to your Rocket.Chat workspace.

Login to your workspace on Rocket.Chat and you will be able to notice the marked bug in the set channel assigned to the set person. All the data you provided through Lambdatest form would already be presented in it. LambdaTest automatically includes test environment details and related screenshots in the screenshot as attachments.

A clickable link will be provided in the rocket.chat channel along with the screenshot to instantly route users on their browser for a full screen view of the bug.

How To Remove Rocket.Chat Integration?


You can work with one integration at a time. So if you would want to integrate to a similar 3rd party application, then you would have to remove your current integration. Here is how you can do that.

Step 1: Login to your LambdaTest account.

Step 2: Select ‘Integrations’ from the left navigation menu bar & go to ‘Communications’ category. This will guide you to a screen where you will find 3rd party applications, available to integrate with your LambdaTest account.

Step 3: Hover to Rocket.Chat block. A “REMOVE” button will appear. Click on ‘REMOVE’.

That was all you need to know for LambdaTest + Rocket.Chat Integration. Increase your productivity multifold with our integrations. If you still have any questions for us, please feel free to let us know. Our experts are always available on chat to help you out with any roadblock regarding our product. Happy testing!

Drone CI Integration with LambdaTest


Drone CI is one of the most popular modern open-source CI/CD tools. It not only provides a continuous integration with your projects but also provides a distributed CI/CD pipeline, which is not possible with some other tools like Jenkins. So Drone is the first choice for many teams as it is a purely distributed, cloud-native, DevOps friendly, team-oriented, and highly scalable open-source CI/CD tool.

LambdaTest now integrates with Drone CI to boost your go-to-market delivery. You can perform automated cross-browser testing with LambdaTest to ensure seamless code render through an online Selenium grid. LambdaTest provides 2000+ real browsers running through machines, on the cloud. You can perform automation testing in parallel with LambdaTest’s Selenium grid which in turn can help you to drastically trim down your test cycles.

Prerequisites For Integrating Drone CI With Our Online Selenium Grid


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

  1. You need to get a VPN setup from LambdaTest as Drone is not publicly accessible. Please contact our customer support or mail us at support@LambdaTest.com.
  2. Some Global Dependencies, such as:
    • A Git or GitHub repository on which you want to activate the CI pipeline
    • You need to download and install node.js and node package manager or npm. Use the below command to install node.js with homebrew.
    • If already installed, update it to the latest version, using the below command.

    For this article, we have cloned and used this Github repository.

  3. You also need your LambdaTest authentication credentials, which includes your LambdaTest username, and access key. These will be set up as the Secrets for configuring the pipeline. To get your Username and Access Key, go to your LambdaTest automation dashboard and click on the “key” icon left to the help button, on the top right corner.

Activating A Github Repository For CI/CD


To activate and integrate your Github repository with Drone CI on LambdaTest, you need to first setup your VPN port and activate it, since Drone is not publically accessible. Once the VPN is activated, here is the stepwise illustration of how to activate your git repo for CI/CD:

Step 1: Enter URL drone.lambdatest.io on any browser.

Step 2: Authorize your GitHub account to access drone.

Step 3: Click on the Sync button to sync all the repositories.

Step 4: You will see the repository which you want to use after the sync is completed.

Step 5: You need to activate the repository for which you want to integrate Drone CI, by clicking on the Activate button.

You may not be able to activate it for CI/CD. (This is because the drone admin user is robot-lt and this user should be the admin of the repository to activate it for CI/CD). You can try by clicking on the repository and then clicking on the “Activate Repository” button.

After clicking on “Activate Repository,” it might happen that the repository is not activated and states that “There was a problem

To resolve this error, kindly add the robot-lt user as admin of the repository and authorize it to make it activated or ask the owner of the repository to make it active.

Step 6: After enabling your repository, the Settings tab will appear. Check the Trusted checkbox in the Project Settings row (this might not occur if the OAuth is already trusted) and select the Private radio button in the Project visibility row and enter the name of your YAML configuration file (in which pipelines will be defined) in the text box in Configuration row. Here we have entered the “.drone.yml” file name, as we are integrating Drone CI.

Step 7: Add the Secrets that are required to execute the Drone CI. These secrets are sensitive information for the repository, such as passwords, tokens, keys, etc. You can add your own secrets in the repository secrets on the Drone server by using the drone-cli. Also, you can add these secrets from drone UI in the Settings as shown below.

(Note: Do not forget to check this allow pull request checkbox if you have any build step to be executed on the pull request.)

Congratulations!! Now you have successfully activated your repository for CI/CD.

Running Tests Using Drone CI with LambdaTest


Now we will see an example in which we will be creating a LambdaTest Tunnel and install node in it. For this, make a YAML configuration file as see shown below:

Let’s try to understand what’s written in this YAML file by deconstructing it into multiple steps.

  • First of all, we are defining what type of pipeline is this.

    We are making a docker pipeline so here the type defined will be docker. (Note: To make another type of pipeline you may check drone official documentation and steps will be almost similar.) We will also give a name to our pipeline. Here, we have given the name “Build”.

  • Now we are defining when this pipeline should be executed.

    Here the pipeline will be triggered when the event will be a push event received through the webhook. This can be changed to pull events, commit events, etc as well. (Note: To see the full list of ways and events to restrict over pipeline execution kindly refer to official documentation)
  • Now we will be defining the pipeline steps by using the steps key in the YAML file. steps: Under this, our steps will be listed
    Step I:

    Here we are giving a name to our step, i.e. “Tunnel”. Image is used for builder containers and commands are the steps to be executed to connect to the LambdaTest Tunnel, build our source code, and make it executable. Here the LT_ACCESS_KEY and LT_USERNAME are fetched from Secrets.
    Step II:

    In this step, we are just installing node on our LambdaTest Tunnel.

    Similarly, we can also write a Test to deploy our executable formed in the build step to s3 using the s3 plugin. (To see the full list of supported plugins and their documentation refer to this link.)

    Here AWS credentials are fetched through the secrets.

Now push your code and enjoy the CI/CD pipeline.

Execution Of The Drone CI Pipeline


Below is the step-by-step execution of the Drone CI pipeline.

  1. Edit the “.drone.yml” and add the code as discussed above.

  2. Once the edit is complete, click on “Commit Changes” to save and commit the changes made. Drone CI is activated as soon as this step is done since we have used “push event” for triggering the Drone CI.

  3. As soon as the Drone CI is triggered (through push event in this case), a new activity can be seen in the “ACTIVITY FEED” tab. The current status of this activity will be “running” or “executing”.

  4. The series of execution of steps includes cloning, followed by the provided tests in the .drone.yml file. For example, we have provided two tests by name “Tunnel” and “SampleTest”. Hence the series of steps to be executed will be:
    • Clone
    • Tunnel
    • SampleTest

    Drone provides functionality of default clone in its workspace, and we are using the same.
    If you want to restrict the default clone in the pipeline and want to use your custom clone then you can add below-mentioned YAML snippet to restrict the clone.

  5. Now based on the tests in the .drone.yml file, this activity can pass or fail. If passed, a green tick will appear on the left of the activity name. Else if failed, a red cross will appear instead, as shown below.

  6. You can view the status and details about each activity by clicking on it. After opening an activity, you can click on any of the passed or failed test cases to view the log. For example, in the below image, we have clicked on the failed test “SampleTest” and its log has appeared on its right.

  7. A successful activity will have a green tick on its left in the ACTIVITY FEED as well on the left of each step and tests.

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. This would significantly trim down the time taken on your cross-browser testing activities. For running test in parallel, add the below command when you update the pipeline’s yaml file, i.e. .drone.yml file.

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

Redmine Integration


Redmine is an open-source, cross-platform, and cross-database project management tool. It is coded in Ruby on Rails, and it helps in collaboration, bug tracking, managing multiple projects, and allows users to have numerous roles. It has an issue tracking system that enables developers to identify each issue status and prioritize it accordingly. Besides, it has additional features such as email notification, feeds, wikis, forums, and time tracker.

Using LambdaTest integration with Redmine, you’ll be able to log bugs in your Redmine project from LambdaTest in just one click. You can grab a screenshot of a problem, highlight an exception, annotate additional detail, select an assignee, include a fitting title and a summary to help convey further actions. You can do all of this directly from LambdaTest.

How to Integrate Redmine with your LambdaTest account?

Step 1: Login to your LambdaTest account. You would need to have Admin or User level access to see and install integrations.

Step 2: Select ‘Integration’ from the left navigation menu bar. This will guide you to a screen where you will find a list of third party applications, available to integrate with your LambdaTest account.

Step 3: Click on ‘Add’ under the block that says ‘Redmine’.

Step 4: Once you click on add, you will be guided to the screen below. You will be prompted to enter your ‘Domain’ and ‘API token’.

  • What is Domain?
  • The domain name is any website’s name having unique IP address that the user enters in the URL tab. It helps you recall the name of the website. You can select a domain name based on your organization’s work area.

  • What is an API Token?
  • When two different applications communicate, a server-to – server connection is established. The API token is used to authenticate user identity from one server to another by extracting user-owned resources accessible on the server from where the communication is initiated. The API token is required to preserve the protection and integrity of any application. They’re just as valuable to the end user as they are to the application. API tokens are important if the end user logs to the application via a two step authentication process.

  • Where can I get my API Token?
  • Make sure you have your Redmine credentials. If not registered, you can register yourself by navigating to the ‘Register’ button on the top-left, then login to your Redmine account and click on ‘My Account’ on the top-left. Navigate to ‘Show’ under ‘API access key’ header on the left. Copy this API access token as you will need to provide it on the LambdaTest application to integrate with Redmine. This API token is auto-generated though you can regenerate it as per your need.

Step 5: Then enter your ‘Domain’ and paste the ‘API Token’ into the field provided at LambdaTest & press the ‘Install’ button.

Step 6: Go to Integrations again and you will be able to notice a green tick indicating that Redmine is successfully installed. You are all set to experience one-click bug logging to share your issues directly from your LambdaTest account to your teammates on Redmine project.

How to Mark your First Bug through Redmine Integration?

Step 1: In order to log bugs from your LambdaTest, firstly you would have to create a Project in the Redmine environment by navigating to ‘Projects>New Project>Create’.

Step 2: Go for any of the test from the LambdaTest’s left navigation menu. For demo, we will be taking ‘Real Time Testing’ option. After that, enter a URL of the web-app you need to test in the dialog box. Then, select any configuration for browser and operating system of your choice & click on ‘Start’.

Step 3: After the VM is launched and operable. You can perform testing on your web-app for finding bugs. If a bug gets revealed, then you need to click on the ‘Bug icon’ from the left panel for capturing a screenshot of the same.

Step 4: After a screenshot is captured, you can annotate any issue or a task with an in-built image editor. Once you are done highlighting the bug, click on the button that says ‘Mark as Bug’.

Step 5: After clicking on ‘Mark as Bug’ button a form would open up. Fill the fields as per your requirement.

  • You can select the name of your ‘Project’.
  • You can choose the ‘Assignee’ to whom you would assign your project.
  • You can assign the‘Priority’ of your task.
  • You can give suitable‘Subject’ for your test.
  • You also get to post a ‘Description’ to help relate the cause of the issue.

Step 6: Click on ‘Create Issue’ & observe it being successfully marked through a single click effort. Once you press the button, you will get prompt messages on top of your Virtual Machine indicating the progress of bug logging. You will get a prompt message in few seconds mentioning Bug successfully marked indicating that the card has been generated in your dashboard.

Step 7: Visit your Redmine dashboard by navigating to ‘Home’ button on the top-left. Select your project and you will be able to notice the logged issue right away in the ‘Issue tracking’ section.

Step 8: To view the log bug details, navigate to ‘Issues’.

Step 9: Then click on the subject’s name by navigating to ‘Subject’, that you have assigned while creating your ticket.

You will find all the data that you provided through LambdaTest already presented in it. LambdaTest automatically includes test environment details and related screenshots in the card as attachments.

How to Remove Redmine Integration?

You can work with one integration at a time. So if you would want to integrate to a similar third party application, then you would have to remove your current integration. Here is how you can do that.

Step 1: Login to your LambdaTest account.

Step 2: Select ‘Settings’ from the left navigation menu bar & click on ‘Integrations’. This will guide you to a screen where you will find 3rd party applications, available to integrate with your LambdaTest account.

Step 3: Click on ‘REMOVE’. You can find the remove button right under the ‘Redmine’ block which would be highlighted with a green tick.

That was all you need to know for LambdaTest + Redmine Integration. Increase your productivity with our integrations. If you still have any questions for us, please feel free to let us know. Our experts are always available on chat to help you out with any roadblock regarding our product. Happy testing!

LEAPWORK Integration with LambdaTest

LEAPWORK is a test automation platform that provides easy and completely visual codeless automation. With LEAPWORK, you can build test automation cases without writing a single line of code, transform those test cases into an automation flow for faster and greater coverage. It also provides seamless integration to various CI/CD and DevOps tools.

LambdaTest has integrated with LEAPWORK to make your test automation more seamless than before. Now, you will be able to perform cross browser testing for over 2000+ browsers, devices, and operating systems at the click of a few buttons. Test automation was never so easy!

How To Integrate LambdaTest With LEAPWORK?

LEAPWORK assigns ‘Agents’, or available machines, for you to execute automation flows. These ‘agents’ can then be used to set up ‘Schedules’ or run automation flows. In order to integrate LEAPWORK with LambdaTest, you will need to create an agent with web-only capabilities for LambdaTest.

Step 1: In LEAPWORK Studio, go to ‘Agents’ section and select New.

LambdaTest With LeapWork

Step 2: Choose Agent type- LambdaTest from the drop-down menu.

Step 3: Log in to your LambdaTest profile, if you haven’t done that already sign up right here.

Step 4: Go to your profile in the top-right corner. Fetch the username and access token key for the next step.

Step 5: Go back to LEAPWORK Studio, where we selected LambdaTest in Step 2 and this window popped up.

As you already know, LambdaTest provides cross browser testing on more than 2000 devices, browsers, and operating systems. You can choose to perform manual as well as automated browser testing on our cloud-based platform.

This is where you-

  1. Provide a title for the Agwent, e.g “LambdaTest” or anything that you like.
  2. Provide the IP address, machine name, or DNS name for the LambdaTest’s Hub.
  3. Specify LambdaTest Port – the default is 80.
  4. Enter your LambdaTest username and access (refer- Step 4.)
  5. Specify the desired “Platform & OS.” A drop-down will appear once you navigate to that section.
  6. For the selected platform, specify the platform version from the drop-down list on which you would like to execute the test.
  7. Specify the browser from the drop-down list on which you would like to execute the test.
  8. You can specify the browser version if the test has to be executed on a specific version. Otherwise, you can select ‘latest’ which will automatically run the test case on the latest available browser version.
  9. Specify the desired screen resolution to be used while executing automation flows on LambdaTest’s machine.
  10. Lastly, the description is completely optional. You can add some text here to keep the created Agent in mind.

Step 6: Enter your hostname (hub), username, and access key in the highlighted sections. This is the most important part, you can enter the rest of the options according to your requirements. Under the hostname, you just need to enter the following address-

Hub.lambdatest.com

Step 7: Next after entering all the desired specifications, navigate to Test Connection, and click it. If the environment was set up properly, Studio will display Successfully Connected in green.

Now you can go ahead and save the LambdaTest environment in the studio, which can be used anytime for scheduling your automation flows.

In case you face any problems during the integration or have any other questions, reach out to us on our 24×7 chat support.

Happy testing!

Favro Integration


Favro is a project management and collaboration tool set up by serial deep tech entrepreneurs. It works under an agile methodology that helps in planning, execution, collaboration, and creation to enhance the workflow of your organization. You can create your dashboard where you can track your various projects, interact, respond to ideas, handle projects with your teammates using multiple kanbans, timelines, and sheets.

The LambdaTest Favro Integration allows you to create a task directly to your specified Favro dashboard from LambdaTest platform. Share your UI observations and input with your teammates anytime, by capturing a screenshot, even in the middle of your test session. You can annotate the screenshot & highlight your issue or input. The fields populated by you when marking as bug through LambdaTest are displayed as information on Favro for that testing instance.

How To Integrate Favro With Your LambdaTest Account?


Step 1: Login to your LambdaTest account. You would need to have Admin or User level access to see and install integrations.

Step 2: Select ‘Integration’ from the left navigation menu bar. This will guide you to a screen where you will find a list of 3rd party applications, available to integrate with your LambdaTest account.

Step 3: Click on ‘ADD’ under the block that says ‘Favro’.

Step 4: Once you click on add, you’ll redirected to the below screen. This will ask you to enter your e-mail address and API token.

  • What is my Favro E-mail?
  • In this field you need to specify the email id through which you sign into your Favro account.

  • What is an API Token?
  • When two different applications interact with each other, a server-to-server communication is established. API token is needed for authenticating user identity from one server to another, by fetching user-owned resources available on the server from where the communication is initiated. API token has been a necessity for maintaining security and data integrity of any application. They are just as vital to an end user as they are to an application. API tokens are relevant if an end user logs in an application through a 2-step verification process.

    If you are logging into Favro for the first time, then you can generate a token for yourself by just entering a name of your choice.

Step 5: Login your favro account and navigate to ‘My Profile’ on the left.


Step 6:Navigate to ‘API Token’ on the left in the My Profile section.


Step 7: Click on the ‘Create New Token’ button.

Step 8:Enter a name in the provided field and hit the ‘Create Token’ button.

Step 9:Once your API token is generated, copy the same by clicking on‘Copy to clipboard’.

Step 10: Then enter your e-mail address and paste the API token into the field provided at LambdaTest & hit the ‘Install’ button. If you are using ‘Self hosted’ Favro instance, instead of API token, you would just have to add your favro login password.

If you are not logged into Favro then you will be redirected to the below screen. Kindly login to your account via gmail or create your account by given option.


Go to ‘Integrations’ again and you will be able to notice a ‘green tick’ indicating that Favro is successfully installed. You are all set to experience ‘one-click bug logging’ to share your issues directly from your LambdaTest account to your teammates on Favro project.


How To Log Your First Bug Through Favro Integration?


Note: If you are using Favro for the first time, then make sure to create a project for yourself. It is a pre-requisite in order to push screenshots from your LambdaTest account.

Step 1: Go for any of the test from the left navigation menu. For demo, we will be taking ‘Real Time Test‘ option.

Step 2: Present a URL of the web-app you need to test in the dialog box. After that, select any configuration for browser and operating system of your choice & hit ‘Start‘.

Step 3: After the VM is launched and operable. You can perform testing on your web-app for finding bugs. If a bug gets revealed, then you need to click on the ‘Bug icon’ from the left panel for capturing a screenshot of the same.

Step 4: After a screenshot is captured, you can annotate any issue or a task with an ‘in-built image editor’. Once you are done highlighting the bug, click on the button that says ‘Mark as Bug’.

Step 5: After clicking on ‘Mark as Bug’ button a form would open up. Fill the fields as per your requirement.

  • You can select which organization should the ticket go under.
  • You can choose from the collection to create dashboards to manage your tasks.
  • You can choose from the widgets to design your workspace.
  • You can specify the testing phase in the widget column.
  • You can give suitable title for your test.
  • You also get to post a description to help relate the cause of the issue.

At the bottom of the form you will find a button ‘Create Issue’.

Step 6: After you click on ‘Create Issue’, you will be able to observe it being successfully marked through a single click effort. You will get ‘prompt messages’ on top of your Virtual Machine indicating the progress of bug logging. After few seconds you will be notified with a prompt message ‘Bug successfully marked’ indicating that the screenshot has been pushed to your workspace.

Step 7:Visit your dashboard. You will be able to notice the logged issue right away! All the data you provided through Lambdatest would already be presented in it. LambdaTest automatically includes test environment details and related screenshots in the screenshot as attachments.

Click on the ‘Testing’ Widget Column and you will find all the data that you provided through Lambdatest already presented in it.

LambdaTest automatically includes test environment details and related screenshots in the card as attachments.

You can add your team members by navigating to ‘Members’ on the top-left.

How To Remove Favro Integration?


You can work with one integration at a time. So if you would want to integrate to a similar 3rd party application, then you would have to ‘remove’ your current integration. Here is how you can do that.

Step 1: Login to your LambdaTest account.

Step 2: Select ‘Settings’ from the left navigation menu bar & click on ‘Integrations’. This will guide you to a screen where you will find 3rd party applications, available to integrate with your LambdaTest account.

Step 3: Click on ‘Remove’. You can find the Remove button right under the ‘Favro’ block which would be highlighted with a green tick.

That was all you need to know for LambdaTest + Favro Integration. Increase your productivity with our integrations. If you still have any questions for us, please feel free to let us know. Our experts are always available on chat to help you out with any roadblock regarding our product. Happy testing!

Selenium Testing With Concourse CI And LambdaTest


Concourse CI is an open-source CI/CD tool which is triggered over Docker containers. It offers a scalable and straightforward solution to your CI/CD pipelines with an intuitive UI that allows you to analyze the dashboard and validate your build execution. Offering a container-centric approach, Concourse CI offers a sturdy pipeline as each task in every job is handled in its container, controlling its dependencies.

Concourse CI can be integrated with LambdaTest to perform automation testing with a cloud Selenium Grid of 2000+ real browsers for mobile and desktop. This document will help you understand how you can integrate your Concourse CI instance with LambdaTest Selenium Grid for continuous testing.

Prerequisites

  • A LambdaTest account. It is free to get started. Sign up now.
  • Install NPM(Node Package Manager). 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.
  • 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:
  • Install Concourse and start a Concourse server at port 8080 i.e. http://127.0.0.1:8080.
  • Install fly CLI tool for Concourse CI/CD. We recommend using the latest fly version, you can check the fly version using:

Configuring Concourse-CI Pipeline


Open your terminal or command prompt. Login to your Concourse server and save the target.

Next, we need to update the environment variables in the YAML file. To access your YAML file, you need to go to the project-folder/concourse-ci. Here you will find the YAML file i.e. pipeline-config.yml.

After you specify the right configuration in the pipeline-config.yml, you now need to create your concourse pipeline with the help of fly CLI.

Now, you will find the nodejs-selenium-sample pipeline in the Concourse Web UI. You can run the pipeline over LambdaTest Selenium Grid from the UI itself.

nodejs-LambdaTest-sample-pipeline

After you trigger the test, you will notice the different stages of test execution. The Concourse CI will get the nodejs-selenium-sample and execute it on LambdaTest after installing the right dependencies.

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