The first is that it is written and maintained by the folks behind the Chrome dev tools, so I'm guaranteed a life-time of support (until Chrome dies out, which is not in the near future), and it is really easy to work with.Īnother reason is that at home I'm working on a windows laptop with WSL (on which I'm running zshell with oh-my-zsh). I chose puppeteer as my end-to-end framework for several reasons. I encourage you to read his article as well.

I do want to give a shout-out to Nick Taylor, who published his article on the subject, and laid the ground work for my efforts here.

The whole thing only took roughly two days of intermittent work, and I think the results are quite awesome. It also integrates beautifully with any Github repository you already have. In this guide I'll show you how to create such a pipeline yourself.Īs my CI platform, I chose Github Actions, as it is super easy to work with. My main goal was to allow automatic dependency updates using Dependabot.

Lately I've added continuous integration to my blog using Puppeteer for end to end testing.

Download free jest puppeteer