Welcome to the 77th issue!

Today, I want to share with you an amazing gem that I found this week.

It's a set of Guides for Software Engineers by Kamran Ahmed.

Honestly, I haven't seen a resource explaining things so simply, so well before.

But that's not all.

There are wonderful Developer Roadmaps, too.

And the best thing yet — the QA Roadmap is coming out soon. Can't wait!

I'll keep you posted.

Happy testing!

Dawid Dylowicz

Having healthy relationships with other team members is very important to our jobs. Rafael Bandeira gives some good pieces of advice that will help you achieve that from the tester's point of view.

The other thing that can help you is Ben Hosking's thorough article about The 12 types of software developers, how to work with each type effectively.

Here's a great article by Paul Gerrard on what it means to be a tester in Agile and how to achieve the whole-team approach to quality.

Reflections are a powerful tool that Sherry Hsu proves by sharing with us plenty of insightful hints and pieces of advice on the testing role, the proper mindset, recommended resources and much more.

Michael Bolton makes an excellent point that, as testers, we should be focusing on problems rather than checking correctness.

In a similar fashion, Alan Richardson answers the question: Do you have to be negative to be a tester?

The days of testers responsible solely for finding bugs are long gone. There's much more to our role, and Patrick Prill explained it very well.

With this clever (re)definition of functional testing, Eran Kinsbruner gives an example of why we shouldn't limit ourselves with the commonly accepted and often confusing software testing terminology.

Whether you're preparing for a technical interview or just want to check your knowledge about Selenium, Yash Tiwari prepared a handy list of 50 questions.

Paulo Oliveira gives a ton of pieces of advice on building a test framework, listing out some popular approaches, and describing the pros and cons of each.

Here's yet another part of the helpful series on improving Selenium tests. This time, Zhimin Zhan shares plenty of code examples for achieving better test maintainability.

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

When you join a new company or a team, you may find some legacy test framework in place. Should you replace, improve or leave it as is? Karishma Sharma provides some answers for each situation.

I love this illustrated guide to load testing by Constance Armitage. It not only gives great value but also does it in a nice, visual way.

Also, I highly recommend reading the first part.

Wondering how to do visual testing for the web apps? Rafael Anachoreta shares a great overview of setting up the tests in Cypress combined with some lessons learned.

If you're looking for a load testing tool, this comprehensive overview prepared by Aymen Eon Amri might help you choose.

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

As I mentioned a few months ago, Protractor will stop being developed at the end of 2022. So what other tools for web testing can you use? Colby Fayock prepared a nice list with a lot of code examples.

What happens when you combine Selenium Grid with Docker Swarm? Sahil Goyal shared a great guide explaining how it can help you run tests at scale.

If you want to understand the importance of unit testing in less than 2 minutes, this magical video by Benjamin Bischoff gives an excellent explanation.

Following up on the great collection of videos on testing in the Apple ecosystem that I mentioned two weeks ago, Gio Lodi prepared his own overview of what new features for testing Apple introduced this year.

Oops, this was production...! 😅

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