LambdaTest Introduces Screenshot API For Faster Visual Automation Testing

Harshit Paul

Posted On: July 23, 2019

view count22513 Views

Read time10 Min Read

Howdy Testers! Today, we are out with one of the most demanded features by our customers. This product update brings you Screenshot API that will help you build powerful visual regression testing applications or screenshot based test reporting. You can also leverage the screenshot APIs for monitoring, reporting, or even version control. If you are an existing LambdaTest customer, then you may already be aware of Automated Screenshot Testing on LambdaTest. For the uninitiated, Screenshot testing is a feature at LambdaTest platform that allows you to capture full-page screenshots of your web-application on multiple different desktop and mobile browsers, with a single click. Not only does it help in visual regression and performing cross browser testing, but you can also use the feature to check the responsiveness of your webpages.

A typical Screenshot test session would involve the steps below.

  1. Open up
  2. Enter the URL for which you wish to perform cross browser testing.
  3. Hit the Capture button to start check screenshots on the selected browsers + OS combinations.
  4. If you encounter any UI anomaly then highlight it inside the screenshots before you share it to your project management tool(optional).

Screenshot Testing Process

This process as you may notice requires a few manual efforts. For advanced users who wanted truly automate their reporting and visual regression pipelines, this was just not enough.

Until now that is.

If you’re new to Selenium and wondering what it is then we recommend checking out our guide – What is Selenium? If you are preparing for an interview you can learn more through Automation Testing Interview Questions.

LambdaTest Automated Screenshot API

Now you can leverage LambdaTest Automated Screenshots API and generate multiple screenshots for a URL of your choice, and that also across multiple desktop and mobile browsers. All with a single API call. Meaning you can avoid the UI entirely and you can embed LambdaTest full page screenshot feature in your testing or even product pipelines.

But that’s not all, in this post, we will look at how you can leverage LambdaTest Screenshot API for capturing full page screenshots of your desired testing URL, in bulk.

With this Screenshot Testing Tutorial, you will learn how to perform Automated Screenshot Testing on the LambdaTest platform.

Boosting Daily-Basis Productivity With Screenshot API

Delivering a cross browser compatibility testing tool, we understand the pressure involved in narrow release windows. Every minute may seem like an hour as a release window draws near, and this is when convenience comes as a comfort.

LambdaTest Screenshot API offers you the convenience of capturing headless screenshots in bulk on multiple (OS + browser) combinations, without even logging into the LambdaTest platform. Simply, generate a JSON file into your favorite API development environment, including the relevant configurations needed for running screenshot testing on LambdaTest, invoke the API and you are done!

You can also use our open Screenshot API document and execute your test cases directly from it.

Not only can you invoke the tests on LambdaTest but you can also download these bulk screenshots as a zip file. You can even define a particular screen resolution to perform cross browser testing. In case you wish to stop any screenshot test midway, you can do that too!

Perform automated screenshot testing for locally hosted web pages or web applications with basic authentication enabled. Invoke a callback URL and send the screenshots to a particular IP or URL, if you wish to share the test results with your colleagues.

LambdaTest Screenshot API would allow you to maintain a daily check on your web application & paddle faster through your release cycles by evaluating your code changes, prior to pushing them to production.

Everything That You Can Do With Screenshot API!

Now, we will look into everything you can perform by executing LambdaTest Screenshot API for generating headless, automated screenshots of your website in various browser & OS. Let us deep dive into parameters involved for invoking these Screenshot API. We will look into syntactical differences & what these differences would empower you with.

Screenshot API

Visit our Screenshot API document from here.

Note: The computed URL for Screenshot API would be

With that said, let us get to the action.

All Operating Systems + Browsers Combinations

To get a list of OS + Browser combinations available on LambdaTest, simply execute the below GET request.

Requested URL:

Client URL would be as followed:

As you execute, you will find the Server response presented below. You can extract the server response in a JSON file.

See Also: 10 Must Try Features Of Automated Screenshot Testing On LambdaTest

Get All Available Screen Resolutions

To get a list of all the available screen resolutions provided by LambdaTest for you to perform cross browser testing, you would need to execute the below GET request.

Requested URL:

Client URL would be as followed:

As you execute, you will find the Server response presented below. You can extract the server response in a JSON file.

Get Screenshots Of An Executed Test Session

In case you wish to fetch all the details from an already executed screenshot test session. These details would comprise of basic test details under which you will have screenshot details for every screenshot captured in your test session.

Test Details:

  1. Test ID
  2. Test status
  3. Defer time
  4. Tested URL
  5. Callback URL(if any)

Screenshot Details:

  1. Operating System
  2. Browser
  3. Browser Version
  4. Status
  5. Screenshot URL
  6. Thumbnail URL
  7. Activity ID
  8. Resolution

Requested URL:

Note: Test ID is a mandatory field for making use of this GET request. This would fetch details in JSON format for all bulk screenshots captured in a test session specified by you.

Client URL would be:

Example Value:

With this Visual Testing Tutorial, you will learn how to perform Smart Visual UI Testing on the LambdaTest platform.

You can complete automated visual testing more quickly with Lambdatest. To guarantee deliveries without bugs, compare screenshots using automated visual testing.

Furthermore, by using its advanced options, our screenshot comparison tool makes it simple to compare the Baseline and Test Output.

Start A Screenshot Test

The bread & butter of a tester. Now, we are going to start a screenshot test through API. With LambdaTest Screenshot API, you can perform cross browser testing on your locally hosted web pages, web pages with basic authentication. You can even provide a Callback URL. We will be talking about each one of these but first, we kick off with a basic screenshot test session.

To start a screenshot test using the API, you would need to trigger the below POST request.

Client URL would be as followed:

Example value:

Screenshot Testing For Locally Hosted Web Applications

To perform a screenshot test on your locally hosted web applications, you would need to declare the below parameter in your request before specifying the configurations.

"tunnel": true,

Example Value:

Screenshot Test With Basic Authentication

Similarly, to perform a screenshot test on a web application with basic authentication, you would need to declare the below parameter in your request before specifying the configurations.


Route Test Details To Your Colleagues Through A Callback URL:

By specifying a Callback URL, you can route your test details to a specific IP, or a specific URL. This would help you to share your test results with your colleagues or to keep them on a specific URL, so you could come back and assess these results when you have time. To invoke a Callback URL, you would need to declare the below parameter in your request before specifying the configurations.

Example Value:

Stop A Screenshot Test

In case you wish to stop a screenshot test, you can do so with the help of a PUT request. Test ID is again mandatory over here as you need to convey which particular screenshot test would you want to be aborted.

Requested URL:

Note: This will terminate only a running test session. Providing a TestID of an already completed test session will provide you with a 404 error as the server response.

You can also refer to the below video tutorial on How To Take Screenshots In Selenium testing.

No Need To Write Selenium Code For Full Page Automated Screenshot

Writing Selenium based scripts to take full page screenshots across multiple different browsers and browser versions is a really tough task. We know. Been there done that and we can attest that its challenge as hell. Some browsers support full page screenshots directly however for most Selenium by default takes screenshots of the viewport only. For these browsers to take full page screenshots, you have to automatically scroll the page, take pixel perfect screenshots of each viewport scroll, and then stitch the images for one single full page. Add in the complexity of making sure that you have the right Selenium versions, and you get yourself a proper Cross Browser Compatibility spaghetti mess.

Fortunately for you, now you won’t have to create such scripts. You can leverage our Automated Screenshot APIs. Our Screenshot feature works using Selenium in backend and we have created individual scripts for each and every browser, browser version and operating system environment. To iterate again, these are all full page screenshots taken on real browsers running on real operating systems.

What To Do If You Want To Build User Facing Web Application?

Not only can you use this for visual cross browser testing, but you can also build powerful end-user products using these APIs. But for that, it’s important to understand the concurrency limits.

The number of separate screenshot sessions that you can run at a time would be defined by your plan’s concurrency. For example, if you have 4 concurrencies you can use the screenshot APIs to run 4 screenshot test sessions with up to 25 different configurations in each session. If you start the 5th test before any of the above 4 sessions complete, your post request would be rejected.

If you are planning to build customer-facing applications using these APIs, do contact us. We would be happy to help you in choosing the right concurrency plans for your applications.

That Is All For Now, Stay Tuned For More!

LambdaTest Screenshot API has been awaited on our platform & having made it live, we look forward to hearing your feedback. Do give it a spin & share your invaluable suggestions to help us create a better cross browser testing environment for all of the testing community. You can provide your suggestions or queries to us by writing to or by simply giving a shout to our 24×7 customer chat support.
We are constantly working to bring more product updates on our platform with the aim of fulfilling all your testing needs under one roof. On a side note you can highlight visual changes to identify errors and deliver pixel-perfect websites through our Screenshot Comparison Tool. Stay tuned for our upcoming product updates. Happy testing & adios! 🙂

Author Profile Author Profile Author Profile

Author’s Profile

Harshit Paul

Harshit works as a product growth specialist at LambdaTest. He is also an experienced IT professional, who loves to share his thoughts about the latest tech trends as an enthusiast tech blogger.

Blogs: 79