Operations | Monitoring | ITSM | DevOps | Cloud

Especially when AI is writing more and more of your code Let’s be honest: developers don’t test enough. You see it every week — a feature is merged, staging breaks, and the bug was something obvious: a missing dependency, an incorrect flag, a minor logic error that could’ve been caught earlier. With AI tools like GitHub Copilot, Cursor, and Windsurf writing code faster than ever, this problem is only growing. The code output is higher — but the validation often isn’t.

…and why it matters even more in the age of AI-generated code Software development is changing fast. Thanks to tools like GitHub Copilot, Cursor, and Windsurf, developers can now generate large chunks of code in seconds. Product velocity is exploding. Startups are shipping faster than ever before. But there’s a catch: More code ≠ better code.

If you use Checkly, eventually you'll be looking at alerts about something failing, and wonder how to debug a failed check. For most of us, the first thing we want to see is the video of a failed check run. Sometimes, though, our check doesn’t capture video. This guide will cover three common reasons a video doesn’t show up on a check run. This advice is general for Playwright as well as those running Playwright tests on Checkly.

In today’s hectic app development cycles, speed is key. But as teams scale and spread worldwide, and app complexity increases, traditional testing workflows become bottlenecks that can compromise security, increase operational costs, and delay product delivery. Simply sharing APKs or configuring physical test devices isn’t enough anymore – it’s time to rethink how we test and demo Android apps.

Starting from scratch with synthetic testing of your web properties and APIs can be difficult. Questions like “what should we be testing?” will very quickly become exercises in figuring out “how can we actually do that?” which may involve sifting through various elements of the DOM or JSON responses. But there are shortcuts to synthetic testing mastery!

You’ve optimized your QoS settings, fine-tuned your firewall, and even upgraded your bandwidth, but what happens when your network gets hit with 10x the normal traffic? Will it hold up, or will it buckle under the pressure, leaving your users staring at spinning wheels and timeout errors? If you’re an IT pro, you know outages don’t happen during idle hours. They strike when traffic spikes.