We’re heavy end-to-end monitoring users here at Checkly and always experiment with how to architect our tests the best way. Over the past months, we’ve settled on a few workflows that make it much easier to spin up new tests, avoid code duplication, and make the entire test setup easier to manage. One of those strategies is to strictly separate concerns in our tests.
The monitoring and testing of public applications and APIs is challenging by itself. What should you test? How often should you run your tests? And who should be alerted? A scalable monitoring setup includes many hidden details, but technically it’s straightforward. Call public APIs and see if they do what they’re supposed to.
