Hello there! 👋
Welcome to the 186th edition of Software Testing Notes, a weekly newsletter featuring must-read content on Software Testing. I hope this week has been good for you so far.
This week, we will explore:
Developing the Right Test Documentation
Testing with Playwright and Claude Code
Tracking AI system performance using AI Evaluation Reports
Test a Kafka Processor with Gatling
Changing the Conversation About Testability
and more…
📚 Testing
Developing the Right Test Documentation by Chris Kenst
This piece is a reminder that test documentation should serve a purpose, not become a burden. Chris Kenst shares why smallest amount of documentation that helps you do your job well can become a tool for learning and effective testing rather than busywork.
Changing the Conversation About Testability by Maria Kedemo
This is a final post in the “Rethinking Testability” series. In this article, Maria Kedemo reframes testability as a way to reduce friction, improve flow, and enable faster learning.
Also read Part 1 – Testability is about people, not just code, Part 2 – Poor Testability is Everywhere – but we don’t always see it and Part 3 – The triangle of Perception
🔍 More Curated Articles
⚙️ Automation
Stop Writing Flaky Tests: Your Foundational Guide to Async in Playwright by Ivan Davidov
If you’ve ever struggled with flaky Playwright tests, chances are the culprit was asynchronicity. Ivan Davidov digs into why Playwright commands return promises and shows how to manage them with async/await for correctness, speed and try/catch for resilience.
Testing with Playwright and Claude Code by Oleksii Nikiforov
In this post, Oleksii Nikiforov explores how to combine Playwright MCP servers with Claude Code an transform manual and exploratory testing. It is a practical guide showing how this setup bridges the gap between manual exploration and automation.
Furthermore, Slawomir Radzyminski shares few Playwright Agentic Coding Tips
Tracking AI system performance using AI Evaluation Reports by Matt Eland
Matt Eland introduces AI Evaluation Reports in .NET, showing how a few lines of C# with the it’s reporting library can generate interactive HTML “report cards” with data such as fluency, relevance, and coherence, with results stored and tracked over time.
Use Copilot Instructions And Page Objects by Gleb Bahmutov
Copilot can write end-to-end tests, but without context it often guesses wrong, misses important checks, or invents selectors. Gleb Bahmutov shows how to guide it with comments, page objects, and a Copilot instructions file so the agent generates reliable and maintainable Cypress tests.
🔍 More Test Automation Articles
💨 Performance
Test a Kafka Processor with Gatling by Serafino Tudorovici
If you’ve ever wondered how to performance test a Kafka-based message processor, Serafino Tudorovici takes us through a hands-on example using Gatling and shows how to simulate message flows, validate processing, and interpret Gatling’s reports to understand throughput and bottlenecks.
IoT performance testing: Navigating the connected device challenge
This article from gatling explores why traditional testing approaches fall short for connected systems and walks through practical strategies like real device testing, simulation, cloud-based tools, and MQTT-focused validation to help teams build more reliable and trustworthy IoT solutions.
🔍 More Performance Testing Articles
🛠️ Resources & Tools
Kotest — is a flexible and elegant multiplatform test framework for Kotlin with extensive assertions and integrated property testing
bombardier — Fast cross-platform HTTP benchmarking tool written in Go. You can check out how to do Distributed Load Testing using Bombardier
📝 List of Software Testers
Do you create content around Software Testing ? Submit yours blog details here and I will add it to the list.
🎁 Bonus Content
📌 OTHER INTERESTING STUFF
⭐ LAST WEEK'S MOST READ
😂 And Finally,
The AI Developer's Dilemma and Tester's Nightmare 🤣
📨 Send Me Your Articles, Tutorials, Tools!
Wrote something? Send links via Direct Message on Twitter @TheTestingKit (details here). If you have any suggestions for improvement or corrections, feel free to reply to this email.
Thanks to everyone for subscribing and reading!
Happy Testing!
Pritesh(@priteshusdadiya)