People keep asking us here at Checkly if and how AI can help create solid and maintainable Playwright tests. To answer all these questions, we started by looking at ChatGPT and Claude to conclude that AI tools have the potential to help with test generation but that "normal AI consumer tools" aren't code-focused enough. High-quality results require too complex prompts to be a maintainable solution.

Today’s complex, dynamic applications demand rigorous resilience testing. A common hurdle is accurately mimicking real user behavior. This post discusses a possible solution: production traffic replication (PTR), a technique that captures actual user interactions to enhance chaos testing, and the principle of intentionally introducing failures to evaluate application recovery.

This is a guest post from Artem Zakharchenko, creator of MSWJS, an API mocking library for Javascript. He also writes about testing for EpicWeb and on his personal blog. Test flakiness is a big issue. Not only can it be a colossal time investment to detect and fix, but it hurts perhaps the biggest value you get from your tests—their trustworthiness. A test you cannot trust is a useless test. Time spent maintaining a useless test is time wasted; time that could have been spent building.

After spending hours or even days manually testing your software, you may be wondering whether or not there’s a better way. The good news? There is.

Today’s fast-paced development environments require new approaches to testing. Enter continuous performance testing. Unlike traditional performance testing, automated continuous performance testing is part of every build, monitoring the application continuously under increased load. With continuous performance tests, organizations with lots of users can expect to improve the customer experience, prevent major outages, and find and resolve issues faster.