The Clean Test Automation Monthly is a monthly blog post that shares interesting or useful test automation content which I consumed during the current month. This blog post is always published on the first day of the "next" month.
Let's begin!
Test Design
AI and Testing: Using Local Models for Testing demonstrates how we can use local AI models for generating test cases and Playwright tests.
Your API Tests Are Passing. That’s the Problem argues that a green API test suite can create a false sense security, especially, if our test suite contains so called shallow assertions.
Generating code faster is only valuable if you can validate every change introduces a testing strategy that helps us to ensure that rapid code generation won't introduce bugs.
The Testing Pyramid is a Relic. Here is What Actually Works. argues that the testing pyramid doesn't work when we are writing modern distributed systems, and introduces a testing strategy which concentrates on static analysis, integration tests, and observability.
Who Tests the Tests? AI, QA, and the Verification Paradox explains what "don't trust without verification" means if we generate automated tests with AI.
Backend
Writing tests with Claude Code - part 1 - initial results describes what the author learned when he used Claude Code for generating automated tests for a Spring Boot REST API.
UI / End-to-End
Why We Chose Playwright Over Cypress compares Playwright and Cypress, and explains why the author decided to use Playwright.
17 Playwright Testing Mistakes You Should Avoid helps us to write better Playwright tests by identifying 17 mistakes we shouldn't make.
Test IDs are an a11y smell explains why the author thinks that we shouldn't use data-testid and describes how we can write tests which don't require test ids.
Making Code Coverage Work with Playwright explains how we can generate code coverage reports for Playwright tests with @bgotink/playwright-coverage.
Your Tests Are Green. Your App Is Broken identifies a situation where our application is broken even though our tests pass, and provides one possible solution to this problem.
Introducing Angular Testing Library Zoneless introduces the new @testing-library/angular/zoneless subpackage which is basically q trimmed down version of the original Angular Testing Library.