Puppeteer is a Node library which provides a high-Level API to control Chrome over the Dev Tools protocol. Basically, everything you do manually in the browser can be done via Puppeteer. A couple of examples are:
In this article, I will focus on performance and will give you a simple step by step approach on how to start with Puppeteer and create a short HTTP tracing, which is logging all the web browser interactions.
A couple of weeks ago we started an experiment at the client-side to check if Puppeteer can help us with performance testing a web application. Where we first use Jmeter in combinarion with our Selenium Page objects we are planning to switch to Puppeteer. The main reason for this is that the Selenium framework is evolved in such a way it’s not that easy anymore to build a jar from the framework and make it work together with JMeter. Reading about Puppeteer made me curious and is apparently very efficient and easy to script.
Before we start scripting a couple of preconditions need to be in place:
To start scripting a Code editor needs to be available otherwise we are not able to script and run our code. If you don’t have a code editor installed on your device I will recommend you install Visual Studio Code. Visual Studio Code is free and available on Linux, MacOs, and Windows.
After installing our Code Editor we are going to install Node Js. This is needed because Puppeteer is a Node library. When installing Node JS we get immediately NPM installed on our device.
Before we are going to install Puppeteer we are first going to create a project directory:
In this project directory we will install Puppeteer with the following command:
When the installation is done we are ready to code!!
After this, we can make use of the functions puppeteer is offering. We will be able to start a chrome browser, navigate to a specific page and close the browser again:
Let’s check if this works by starting the little script with the following command in your terminal. Don’t forget to use the file name of the file that you created. In my case this is test.js:
If your script runs successfully let’s add some extra steps and do a bit of navigation to the blog section of this web page. Your script will look like the following then:
To test your script you can use the following command in your terminal:
If your script ran successfully it’s time for the next step: we are going to make a HTTP tracing during the execution time of the script. The first action we need to do is to add an extra package with the name puppeteer-har. We can get this package via NPM by the command:
When the package is finished with downloading, we can extend our script with the following code at the top of the script. Your first two lines of code will look like this:
After this is done we will place the code below between the opening of a new page and then set the height and width of the window. In this couple of lines of code, we are creating a timestamp for a unique filename and we are starting the tracing:
To stop the HTTP tracing we need to add an extra line of code at the end of the script:
After you run your script, a Har file is created. The format of the file is basically a JSON object with a particular field distribution. For this example, we are going to use an online HAR Analyzer but be careful. A Har file contains sensitive data like all the information you submitted. For this example everything is fine and we can use the HAR Analyzer from google.
Choose your file and open it. All the requests that happen during your recording will be visible in this analysis.
After following the steps above you are able to
For the next article that I am going to write, we will go deeper into how to set up the TICK stack in a Docker container and send our performance results to an InfluxDB, which is part of the TICK stack. In this way, we can create a dashboard of the available data.
I hope you had fun reading and trying the examples above. If you have questions don’t hesitate to contact me for some support or to write in the comments below.