Monkey Test It by Jesper (@jesperht) from London.
We are happy to offer a 20% lifetime discount to readers.
Simply email Jesper at firstname.lastname@example.org with the subject “Holiday banana discount” and he’ll sort you out 🙂
Offer expires Jan 1, 2019.
What’s your motivation for creating your product?
Monkey Test It is the result of scratching an itch I had experienced at the last 4 companies I had worked at. These companies all had solid testing pipelines, but after the deployment step, testing stopped. In my mind this was a huge gap in our coverage, as all kinds of things can go wrong once a page is live and deployed to production.
I wanted to go beyond searching for strings to see if things “worked”, and that’s when Monkey Test It was born. It started as a broken link checker, but then I added more and more checks as I discovered new bugs that were commonly occurring, while at the same time keeping the interface easy enough for non-tech staff to be able to use it. Today we’ve got thousands of users and some exciting releases planned for the near future!
What are your product features?
* Finds bugs on your website automatically with zero coding involved
* Slack integration
* No infrastructure needed – you can schedule tests directly from within Monkey Test It
* Plays nicely with other systems to trigger automatic tests when you deploy to Heroku, Netlify, or just about any other platform.
When did you launch?
March 11th 2016.
Where did you launch?
How did your launch go?
535 upvotes #1 product of the day.
Got around 2000 new unique visitors on that day, and then an aftershock of 1600 new ones 3 days later (PH Newsletter?), and about a week after got an extra 1000 visitor boost from a middle eastern tech news site that featured us (which I assume they found via PH).
Any specific launch tips? Or things you would do differently?
The launch was rather … unplanned! We were hunted by surprised by someone, and I was at my day job at the time, working on something else when I noticed the traffic spike. Luckily I had virtual machine images created recently, so handling the increased load wasn’t so bad as I just had to spin up more testing servers on the spot.
My main advice would be to set up triggers in your analytics software to alert you if you get a 10%+ traffic spike. Have a plan for how to handle traffic spikes (horizontal scaling? Aggressive caching?). Use something like Sentry (sentry.io) and FullStory (fullstory.com) to understand the issues that users may have when they visit your site.