Welcome to the 277th issue!

AI is now commonly used to create code. So how's the experience of testing it?

I want to share with you some recent thoughts about that from testers and developers:

• Testing AI-coded applications: Practical tips for software testers by Rafaela Azevedo,
• When ChatGPT Writes the Code — and Everyone Thinks It's Perfect by Yuliia Baranetska,
• A programmer yelling at the clouds about vibe coding by Daniel Draper.

In short — pay more attention. 🙂

Happy testing!

Dawid Dylowicz

Sarat Ramineni correctly points out why QA should be a core part of product strategy, not just a final step in development.

Similarly, Alessandra Moreira shares a great reminder about the impact of Engineering Team Culture and Code Quality.

Struggling to understand where your bugs come from? Mona M. Abd El-Rahman shows a good example of building a root cause analysis process in practice.

What impact will AI have on the QA role? It's a valid question, and you can find out what other testers think based on this discussion.

In another thread, someone shared a belief that QA deserves more than just being the last line of defence, which resonated with others.

In Agile, I can't imagine testers working outside of the teams or joining in the late stages of the software development life cycle. Ahmed El-Deeb highlights well why it's important.

Moreover, George Ukkuru describes The Seven Hats of a Test Engineer in modern software development.

How do you decide when and what to automate? If you struggle to answer that, listen to Marina Jordão's helpful advice.

At the same time, Niraj Subedi reminds us What Automation Misses: Bugs Manual Testing Still Finds Every Day.

If you want to prepare to run your test suite at scale, Peyman Iravani wrote a comprehensive guide with plenty of JavaScript code examples.

But remember that 100% of Test Coverage Is Not About the Amount of Tests, as Andrei Trukhin explains.

In previous newsletters, I've featured several articles about test doubles, such as mocks, stubs and fakes. But I haven't covered how to do that in Python yet. Well, today is the day, thanks to Bruce Ho!

Another good read from Alessandra Moreira describing the possible problems and anti-patterns you may find during test automation, offering tips on how to improve them.

Some remedy to that might be Bad Test Hunting — Mutation Testing, as Edgars Garšneks outlines.

Last week, I highlighted an open-source solution for AI test automation. This time, you can learn about more projects thanks to Faris Kurnia.

Furthermore, Mohammad Faisal Khatri put together a handy collection of Top GitHub Repositories to Learn Automation Testing.

Using Cucumber? In this comprehensive article, Irfan Mujagić gives several practical tips on how to improve the maintenance of tests.

Eleonora Belova has just started a series of articles about API testing with PactumJS. You can also read the second part.

How often do you use cy.contains() in Cypress? Sebastian Clavijo Suero explains various scenarios in which there might be a better way.

Furthermore, Josh Grant explains Why I Love Get By Text in Playwright.

Whether you want to get into test automation or you're already on that path, you may benefit from the skills that Daniel Knott describes in detail in this 23-minute video.

Continuing the series of recordings about testing with Playwright, this time Alex Khvastovich shows how to test APIs with that tool.

Furthermore, Karthik K.K. demonstrates how to Automate Complex API Tests with Just One Command using Playwright MCP.

That's AGI... 🤣

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