Welcome to the 270th issue!

This got my attention — What are your thoughts on the future of QA role?

It's a discussion about the evolving responsibilities and expectations of testers and developers during the software development lifecycle.

Should testers become enablers of testing rather than entirely focused on testing?

Perhaps — at least that's more in line with the Modern Testing Principles.

But keep in mind that different companies require different approaches; there's no one-size-fits-all.

Happy testing! 🙂

Dawid Dylowicz

That's a good reminder from Alessandra Moreira about what practices to follow after the software is shipped to mitigate degradation in its quality.

About that, Aya Akl wrote a decent article about Shifting Quality Into High Gear, both left and right.

Simon Knight provides helpful templates and good advice to founders and members of the leadership team on assessing quality.

Speaking of providing the right information to the ones higher up, Mona M. Abd El-Rahman wrote a wonderful piece about Bug Advocacy 101: Make Sure Your Bugs Get the Attention They Deserve.

Simon Prior gives real-world examples and highlights why and how testers should adopt new AI-related practices, tools, and ways of working.

Also, James Bach shares some interesting thoughts: Is There Something in Your "I"?

This is a fine explanation of what Quality Engineering is and why it's important. By Jitesh Gosai.

Emily O'Connor shares a comprehensive overview of the processes and criteria that should be part of the definition of done.

Furthermore, İlay İnan Ünal rightly points out that If There's No Time for Testing at the End of the Sprint, There's No Time Management at All.

Curious about how other companies approach test automation? Harsh Jha demonstrates what they included in their test automation framework.

Also, Muhammet Topcu wraps up a long series of articles on Creating End-to-End Web Test Automation Project from Scratch — Part 6.

Roy Chanunkha shares an insightful perspective on how testing helps them during software development.

Moreover, Reza Akbar Attariq describes the F.I.R.S.T. Unit Testing Principle That You Need to Know

How complete is your API testing framework? Sai Anudeep Adimulapu shows how to build a decent solution with logging and reporting in the JavaScript tech stack, using several open-source tools.

There are many great points brought up by Melissa Eaden about the importance of caring for code, the coverage metrics and the usefulness of dashboards and reports. You can learn more in the second part.

A good follow-up read to that is Petr Plavjaník's insights into Code Coverage: What the Experts Really Think.

Wondering what open-source AI tools and solutions are getting traction in software testing? Saurabh Srivastava put together an overview of some of them.

In relation to that — How do you use AI in your QA teams?

The window.localStorage property is frequently used by web apps. Priyanshu Shekhar shows several ways of leveraging it in Playwright tests.

In another article, Priyanshu also advises to Stop Carrying Selenium Habits to Playwright.

PIT is a powerful tool for mutation testing Java code. Eduardo Kobus demonstrates how to set it up and run with examples.

There's some good advice from Lewis Nelson on how to speed up Playwright test execution on CI.

Another way to achieve that might be Handling Multi-User Flows in Playwright the Right Way, as Mariam Sargsyan suggests.

Cypress, as a JavaScript-based tool, relies a lot on async implementation. Sebastian Clavijo Suero wrote a very thorough overview demonstrating what it entails.

A lot of people use AI to improve test automation. That's fair, but Gil Zilberfeld takes a different point of view, checking how it can help with exploratory testing, too.

Karthik K.K. continues the series of videos demonstrating various AI solutions applicable to software testing. Here's another example of using MCPs to test across different layers of a web application with AI.

Edge cases... 😂

Thanks for reading!

If you like this newsletter and it helps you become a better tester, you can say thanks and buy me a coffee.

Dawid Dylowicz