Welcome to the 284th issue!

Appium is a popular tool for testing mobile and desktop applications.

Recently, they announced a new major version — Appium 3.

And while it's not as groundbreaking as the previous one, it brings some important improvements and breaking changes that you may want to be aware of.

I recommended checking out Ümit Özdemir's article about Appium 3: A New Era in Mobile Test Automation, as well as the Official Migration Guide.

Happy testing! 🙂

Dawid Dylowicz

Good communication is one of the most important skills of testers and Kat Obring gives some great advice on how to do it right.

Furthermore, Faris Kurnia guides us on how to Perform Root Cause Analysis Like a Professional QA Engineer.

Doing valuable test documentation is neither easy nor exciting. However, Chris Kenst advises how to approach it most effectively.

Also, Nureko Wibowo asks — Do We Really Need a Test Plan Before Testing?.

Ady Stokes makes a few good points on why testing is very much about thinking and describes several mindsets that can help you become a better tester.

Moreover, Yogesh Deshmukh gives a sobering explanation of Why Testability, Performance, Security Can't Be Afterthoughts.

Péter Halász shares interesting insights into how moving from testing to development has helped him become a better software engineer.

Testing is more than just tools and automation. Marina Jordão rightly points out that real quality comes from people, strategy, and user advocacy.

Interested in seeing the practical application of AI in testing? Gleb Bahmutov demonstrates using it to pick and run relevant tests.

Similarly, Sh Yin Lim shows how to create A Streamlit Dashboard That Explains Test Case Failures with AI.

Juan Rada challenges the original test pyramid and brings up several points on why it's not always beneficial to invest in tests on the lower levels.

Moreover, Rafal Szymala describes the approach to Microservice Testing That Lets you Sleep At Night.

After years of glorifying microservices architecture, it seems that a modular monolith is taking center stage now. Pani Kumar explains the benefits in testing, quality and developer experience.

Furthermore, Danail Bikovski describes the journey of Designing a Scalable Test Automation Framework for SaaS and its demonstration.

Have you tried doing mutation testing yet? Bas Dijkstra has a good example demonstrating how to implement, run and interpret it.

Writing tests with Playwright is pretty straightforward, but sometimes you may run into unexpected issues. Marius Besel describes how to resolve a problem with missing tests.

Are you using GitHub Copilot? Maxwell Nyamunda shares several tricks that can help you in your day-to-day test coding.

Moreover, Gleb Bahmutov shows how to Use Copilot Instructions And Page Objects to write end-to-end tests.

Want to use AI to write Playwright tests? Sławomir Radzymiński wrote a detailed overview with some great advice on how to do it right.

If you test Spring Boot apps, Philip Riecks has several practical tips on implementing automated tests across all levels.

This opinion has resonated with the testing community on Reddit and people share their experience of moving from Selenium to Playwright.

And in another thread, someone's asking for advice — Best place to learn Playwright automation end-to-end?.

If you want to power your Selenium tests with AI, Karthik K.K. recorded a short video demonstrating the potential capabilities.

Microsoft has recently introduced the Playwright MCP Chrome Extension, and Joan Esquivel Montero briefly explains why it's useful and how it works.

Also, you may want to check out the testing community's Opinions on Playwright MCP.

Vibesort... 😂

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