Skip to main content

Puppeteer Testing With CI/CD

LambdaTest integrates with a variety of CI/CD solutions to help you pace up your go-to-market launch by automating your delivery pipeline. Similarly, you can run Puppeteer tests in CI/CD across 40+ browsers in the cloud, reducing lead time by 10X and shipping quality builds faster.

Running Puppeteer tests through CI/CD pipeline involves three stages:

  1. Build: It consists of developing an web app (or code) and hosting it on a staging environment for testing.
  2. Test: It entails running Puppeteer tests on the LambdaTest platform.
  3. Deploy: Based on your CI/CD configuration, the deploy stage may or may not present.

Running Puppeteer Tests Via CI/CD

LambdaTest offers integration with CI/CD tools like Jenkins, Bamboo, AWS CodePipeline, and more. In order to run Puppeteer tests in CI/CD, you need to perform few steps in the Test stage of your CI/CD pipeline.

  1. Ensure the website (or code) is hosted on staging environment.

  2. Import test data in existing databases in order to initiate the tests.

  3. If the website under test in hosted on local server, then you will need to configure the LambdaTest tunnel by setting tunnel capability to true for running local tests via CI/CD on the LambdaTest. However, if the staging website is publicly accessible then this step is not required.

  4. Ensure your Puppeteer test scripts uses puppeteer.connect method to connect to the CDP endpoint at LambdaTest. Additional parameters for assigning a specific browser and OS combination to your LambdaTest test are contained in the capabilities variable.