Welcome to the 285th issue!

Do you know why testability is important?

Look no further, because Maria Kedemo wrote a fantastic series of articles about it:

1. Testability Is About People, Not Just Code.
2. Poor Testability Is Everywhere — But We Don't Always See It.
3. Why We See The Need for Testability Differently.
4. Changing the Conversation About Testability.

It's a great reminder not only for test engineers, but for all members of software development teams.

Happy testing! 🙂

Dawid Dylowicz

If you're wondering how to bring value to team meetings as a tester, Mona M. Abd El-Rahman gives valuable advice with sample questions.

Moreover, Nureko Wibowo advises creating The QA Document That Could Save Your Job.

Tech debt, like bugs, is an unavoidable part of software development. It's all about managing it effectively, and Ilia Golos shares several tips for testers.

Additionally, Fred Hebert wrote a thought-provoking article about Ongoing Tradeoffs, and Incidents as Landmarks.

Thiago Werner puts it simply — the goal of this article is to prepare you to test AI features by providing a good overview of LLMs, MCPs, prompt engineering and testing practices.

I also appreciate Taras Kizlo's effort to create an in-depth overview of practical tools and aspects of Manual Testing.

A good reminder by Ravisuriya Eswara about treating software development and testing as part of one process and the benefits it yields.

Similarly, Heemeng Foo uses the football analogy to emphasise that Quality is a team sport and Rashmi Wickramasinghe shares a journey of Me as a Quality Enthusiast.

Abdelkader Hassine demonstrates yet another example of leveraging AI to improve test flakiness by self-healing mobile locators.

On that note, Gil Zilberfeld shows the steps of Migrating Test Code with AI: From Frameworks to Languages.

I think Shailesh Kumar was quite humble to call this guide "gentle" as it turned out to be a detailed and comprehensive overview of the fundamentals of testing in JavaScript using various tools, such as Mocha, Chai and Supertest.

David Ingraham came up with a method for assessing test automation maturity in four phases: confidence, short-term feedback, speed of development, and long-term feedback.

Roman Kostenko gives pragmatic advice on how to avoid overengineering your test framework by following some good practices.

Furthermore, Danail Bikovski demonstrates Designing a Scalable Test Automation Framework for SaaS.

It's a fair question since the experience may differ between companies. Several testers shared interesting thoughts about it in this Reddit thread.

Also, How many test cases do you automate?

TestNG is a popular test library for Java. Vaibhav Chavan shares several tips on improving your tests, followed by another guide on Parallel Testing with TestNG.

Roshan Manjushree Adhikari explains how to fight selector-related test flakiness in Playwright. Good advice that can also be applied to other test frameworks.

Using real-like data is important for accurately testing your system from the user's perspective. Sajith Dilshan provides an overview of the Java Faker, which can help you achieve that.

Cuneyt Bati describes the effort of migrating tests from Cypress to Playwright and the slight difference in features between the two.

Moreover, Jennifer Shehane shares that Cy.press() got an upgrade in Cypress 15.1.0 with more actions available.

Testing mobile apps? Joan Esquivel Montero recorded an insightful, 15-minute video describing a whole stack of tools for test automation.

This is a comprehensive, hour-long demonstration of using AI in software testing by Karthik K.K.. Lots of practical insights in one place, especially if you haven't explored that area yet.

Also, have you heard of the new Visual Studio 2026 — AI Infused IDE That Creates 10X Developers?

Si++... 😂

Thanks for reading!

If you enjoy this newsletter and find it helpful in becoming a better tester, please consider sharing it with others.

Dawid Dylowicz