Have you ever worked on a software project and it got more and more complex the longer you worked on it? You started building some features, but once you got to the heart of the big task that has an important business impact, the code already got so complex that you struggle to implement the most important feature. Oh and heck, you realize that there are a couple of things you haven’t thought about before that totally change the game.

Have you ever tested whether all pages of a website return with a 200 status code before you deployed to production? No? Then let me introduce sireg: a tool for website regression testing.

Over a year ago, I wrote an article on how I regression test the sitemap of my website before I deploy an update. Back then, I used a simple unit test setup to download the sitemap, rewrite all links to target the staging server and fire some HTTP requests. While being involved in the relaunch of the website of the company I work for (check it out: www.mimacom.com) I felt I just had to turn the idea of website regression testing into a standalone project. Say hello to sireg! :-)