Welcome to the 84th issue!

How are you doing?

I hope you're well and enjoying the summertime (if you live in the northern hemisphere)!

I'm currently on holiday in the south of France and it's marvellous! ☀️

This might be a well deserved time off from my day-to-day work but mind you, I'm not forgetting about the newsletter.

Because you know what? It doesn't feel like work to me.

It's always a pleasure to read through all the amazing news and share them with you.

So thanks for subscribing, for your feedback and for all the coffees you got me so far.

I truly appreciate that.

Happy testing! 🙌

Dawid Dylowicz

Blake Norrish nailed it.

Note: If you can't access the full article, simply open it in a private tab.

What does bug really stand for? Ravisuriya Eswara makes sure we have a common understanding of this term and he does so in a really good way.

Here's a great article by Gil Zilberfeld on how testers can influence developers to write testable code.

On a similar note, Adrian Brociek described why Removing and simplifying tests is part of development too.

Having good metrics in place is as important as having the performance test itself. Klaudia Dziubek tells us how to achieve them.

And if you need more context, she also shared a valuable article explaining the Basic Aspects of Performance Testing.

Loraine Garutti wrote a wonderful summary of the tester's role in Agile, based on the timeless Agile Testing book. I have nothing to add!

Can't we just leave unit tests? Roger Hill lists six reasons supporting that notion... Only to debunk them one by one. Nicely done!

Similarly, Clément Bataille explains Why we should write unit tests.

Note: If you can't access the full article, simply open it in a private tab.

Antoine Craske wrote a really good article discussing some interesting concepts around test automation — the value, the wealth, the processes and the culture.

Wondering how to generate test data for your tests? Roy Straub has some useful tips about creating your own test data builders.

Additionally, Navpreet Singh shows a great example of the Builder pattern use-case for API automation.

This is an honest and accurate point of view on test automation coming from Piotr Kałuski's vast experience in the field. Hard to disagree!

Note: If you can't access the full article, simply open it in a private tab.

Hui Ching Lim shares an extensive guide to the dos and don'ts of test automation, including several tips on test code and test design. All this is illustrated with examples (as long as you can read C code!).

Choosing a performance testing tool? Mihail Urbanovich lists out eight features that can help you prioritise and choose the best one for your needs.

And if you're looking for a practical example. Ümit Özdemir shows how to combine Karate & Gatling for Performance Testing.

There's no denying that some Chrome extensions can greatly improve tester's productivity while testing web apps. Here's a list of five that Jamaal Todd found useful.

Note: If you can't access the full article, simply open it in a private tab.

TestCase Studio helps you automate writing your manual test cases. Wait, what?! Sanjay Kumar created a tool that records the actions you perform on the web and writes them down in English. Why? So that you can add missing test cases or create steps needed to reproduce a bug.

If you use C# for testing, Curtis Carter has a really handy tip about using Bogus to generate contextual fake test data.

Testing Windows applications? Make sure to check out this comprehensive list of tools prepared by Joe Colantonio to learn which one can help you best in automation.

Just last week ago, Chris Kenst shared a list of conference recordings from 2018, and now he serves us with yet another one. This time, it's about videos from the last year. Thanks!

Are you ready to go back to the office?... 🤣

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