Welcome to the 217th issue!

How do you deal with conflicts in QA?

Ideally, you'd like to know how to avoid them.

But if they happen, you need to know how to navigate them.

So this week, I found some great advice for both cases:

• Types of Conflicts Between QA Team Members and How To Overcome Them by Mihaela Sfat,
• Fostering Positive Working Relationships in Software Testing by Venkat Ramakrishnan,
• Cooperation helps to improve testing, helps testers and helps the company by Mike Harris.

I hope that next time you'll face such a challenge, you'll feel better prepared.

Happy testing! 🙂

Dawid Dylowicz

Learning from their own experience, Michal Langmajer gives practical advice on how to increase the quality of your app delivery.

Similarly, Maaret Pyhäjärvi recognises the importance of faster releases in her recent reflection: Learning the hard way, experience.

Someone from the testing community decided to express an honest opinion on being a tester nowadays. It led to an insightful discussion in the comments with some people sharing their own perspectives.

Callum Akehurst-Ryan shares an important reminder that we shouldn't view testing as an afterthought but rather focus on testing activities early and throughout the software development life cycle.

Furthermore, you have to accept that You may have bugs due to testing, as Jayateerth Katti points out.

It's a great question, and it's good to see both managers and testers sharing their perspectives. That's valuable advice whether you're already a manager or planning to become one.

With this short example, Titus Winters explains how being more specific in test and code design can help you avoid misunderstanding further down the line.

If you're also nurtured by these questions, read on, because James Thomas shares some insightful thoughts on it.

Wondering how to decide what tests to automate? Chamila Ambahera and Sameera De Silva asked themselves this question, did some research, and came up with a helpful scoring method.

Continuing the insightful series on different approaches to test automation, this time Sander van Beek explains the pros and cons of the "Everything" mindset where you mainly focus on automating a lot of tests.

Arman Ahmadi explains why looking merely at the coverage percentage without the context of what has actually been tested can be misleading.

In relation to that, Michael Bolton shares a story of the Inevitability of Bugs: An Example.

The new release of Bun — a lightning-fast, all-in-one JavaScript toolkit — brings some improvements to its test runner capabilities. Irfan Mujagić explains what's new.

Writing tests with Cypress? Then you might be interested in some of the handy plugins highlighted by Sebastian Clavijo Suero.

If you want to learn how to implement contract tests, Aleh Maisevich explains it using Pact.

Similarly, Yash Khare wrote A Not Brief Intro to Contract Testing.

For those of you who thinking of moving towards test automation, Kacper Ciepielewski recorded a helpful 18-minute overview of what it takes and means to become a test automation engineer.

This is yet another great interview by Nikolay Advolodkin, this time discussing AI's impact on development and testing with none other than Jason Arbon.

Users are the best testers... 😅

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