Hey there,

Do you ever get those dreaded emails from a frustrated customer complaining that something has broken in your application? 

Maybe you shipped a new update that broke something you didn't even consider would need testing.

Or maybe a third-party API changed and caused something to break in your app. Facebook and Stripe – I'm looking at you. 👀

If you're like me, these messages cause you an enormous amount of anxiety. I get stressed out to the max when my customers have a bad experience and want to fix the issue as quickly as possible.

If you have to wait for a customer to alert you to a problem, this is obviously BAD!

What if the problem is with your signup form and 99 users abandoned your product before the one who decided to email you and tell you?

Now, you probably know the solution to this problem is writing integration tests and running them every time you make a change to your application.

The truth is, many developers don't write tests, especially when working solo or as part of a small team that doesn't have the time or resources to create tests.

Integration tests are time-consuming and expensive – you have to learn complex testing frameworks and write what seems like endless code to run even basic tests.

And the bad news is – many user errors happen in the browser, so your integration and unit tests don't pick them up.

Do you think your users care that your integration test passed successfully on your server if they're presented with a frustrating error in the UI?

The solution is to use browser tests that mimic the user behaviour and test the complete end-to-end cycle of UI ➡️ API ➡️ Server ➡️ UI.

Creating browser tests is also complex and expensive; you need to learn complicated frameworks like Selenium and write tonnes of code.

Testing is so complicated and time-consuming that most people don't bother, and it's understandable, but this can come at a massive cost when you lose customers and revenue to bugs and problems that should have been detected and fixed before a customer experienced them.

I built Firelab to help developers like you test their web applications without learning complex tools and frameworks and spending weeks writing and configuring tests.

You build your tests in the browser in minutes using an intuitive UI and then schedule them to run whenever you want. No frameworks or code required!

Firelab simulates real user behaviour using a real browser, so you can detect problems that would not be discovered using an integration test running on the server.

Here's how it works:

1. Create a list of actions using the UI, e.g./click form button/

2. Determine what you expect to happen, e.g./HTTP 200 from /api/auth/

3. Select a schedule: hourly, daily, weekly or when your code changes

4. Get alerted as soon as a test fails so you can take action

I'm going to launch Firelab on Product Hunt on Wednesday 28th of June and give a special 50% discount for three months.

BUT, as a Gravity subscriber, I want to give you the discount TODAY.

If you sign up now using this link, you get 100 tests for FREE, and you get 50% off the first three months of your subscription if you choose to upgrade.

What have you got to lose? Give it a try, and if you like what you see, I'd appreciate your support on Product Hunt next week. 🙏🏻

I'll be in touch next Wednesday with an update on the launch 😎


Created with MailerLite