A spicy article hit my inbox the other day. It came with a bold claim — “API testing is better than UI testing”. Absolutes like “A is better than B” rarely hold in the software world. “It depends” is the answer to most tech questions for a reason. Let’s compare API and UI testing and discuss why one isn’t better than the other. The frenemies are “just different”, and always will be. And that’s a good thing.
Today’s a big day at Checkly; we’re thrilled to announce that next to Browser and API checks we released a brand new check type to monitor your apps — say “Hello” to Heartbeat checks! In the realm of software, ensuring uninterrupted functionality is critical. While synthetic monitoring helps you discover user-facing problems early, keeping a close eye on the signals coming from your backend can be just as vital.
When we launched the Checkly CLI and Test Sessions last May, I wrote about the three pillars of monitoring as code. Code — write your monitoring checks as code and store them in version control. Test — test your checks against our global infrastructure and record test sessions. Deploy — deploy your checks from your local machine or CI to run them as monitors.