Using a dockerized setup would be a nice solution, but hey: if I am running windows anyway, shouldn't The problem is that when someone in your team runs the same snaphsots inside Windows, the snapshotsĪre slightly different from the ones produced under WSL/linux (or macos, for that matter): Test script run jest with the puppeteer snapshot steps and enjoy the resulting PNGs. How about this one: running headless puppeteer and saving image snaphots? The basic problemīasically, this shouldn't be that difficult: just go npm run test inside wsl, let the Every once in a while you do, however, notice theĭifference between working inside WSL and a native Linux distro. In a Linux distro, which - thanks to wsl - has become a rather trivial thing I also want my development environment to reside Inside that file, add: module.Call me weird, but I prefer to do all my writing and development from inside To configure Jest, create a file named in your root folder. Now that we have our libraries installed, let's configure them both. If you do not already have a package.json file, create it by running this command: npm init

Installing all three packages is as simple as running the npm install command: npm install puppeteer jest jest-puppeteer -save-dev Installing Puppeteer, Jest, and Jest-Puppeteer If you don't have them installed, follow our how to install Node guide.

If you need a refresher, check out our class on JavaScript. End-to-end testing is an important because it helps ensure your application is working properly from the perspective of your users. In this tutorial, we will learn how to use the Google-built Puppeteer library to control an instance of headless Chrome and the Facebook-built Jest JavaScript testing library to write and run end-to-end testing suites.

Jest puppeteer download