Welcome to the 164th issue!

Recently, someone came up with an idea to ask this openly on Reddit:

Let's share our salaries to see and compare if we are being paid the fair value.

With 200+ comments, it's quite a good reference point across several geos.

Happy testing! 🙂

PS. There was a similar QA Salary Survey 2022 on Reddit back in December.

Dawid Dylowicz

Some incidents are unavoidable, and the best we can do is analyse and learn from them. Sam Cooper gives some advice on that.

That's also why Maciej Rojek tells us to remember The Importance of Observability in Software Testing.

Jeff Nyman takes us on an intriguing, philosophical journey trying to capture what testing is really about.

Similarly, Paul Seaman explains why communication is important for testers and how they can get better at it. Why? Because you asked.

There are some really interesting insights from Maxilect on an experiment of running a team without a tester, including examples of situations they needed to handle.

Meg MacKay explains what team members can do to empower testers in their teams.

In relation to that, Grace Icay shares some honest Reflections Of An Ex-Software Developer, including the misconceptions about testers.

In yet another solid article, Meg MacKay shares a few pieces of advice on what testers should do when entering a new project.

Moreover, Dmytro Stekanov advises you to Study what you test.

Code reviews are an important quality gate. Beth Clarke gives a few tips on how to make the best out of it.

Venkatesh-Prasad Ranganath shares his learnings on fixing flaky tests on the Android platform by tweaking timeouts — a solution that can also be applied in other test automation solutions.

By using a lot of examples, Kostiantyn Teltov wrote a comprehensive overview of each of the SOLID principles in test automation.

Paul Grizzaffi uses a song lyrics metaphor to articulate why we should be cautious with test automation goals.

Similarly, Maximilian Zimmermann explains How much automated testing should be done in software development, and Peter Lupo advises When to keep the tests manual.

Dan Snell shares a great example of how a good design of microservices architecture can influence testability.

Furthermore, Rahul Bhave shares some Best Practices for Test Automation Architecture in Microservices Testing.

Do you use Cypress to write automated tests? Earl Lacsamana has some good practices to share.

And if you focus on API testing, Oscar Cepeda wrote a helpful Guide to start with Cypress API Testing.

Burcu Akkaya describes how to set up, implement tests and generate reports with Karate — an open-source API testing tool.

However, Daniel Delimata suggests that Karate is a tool which pretends BDD but in fact is against BDD principles.

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

Someone on Reddit is wondering what makes people use full-code over low-code solutions to write automated tests. There are some interesting answers.

If you're curious about using Cucumber with Java to write Behaviour-Driven Development tests, check out this getting-started guide by Darmawan Hadiprasetyo.

If you haven't heard of the Selenium BiDirectional feature yet, here's a great overview with examples by Sławomir Radzymiński.

Node has recently released a new node:test runner and here's an in-depth overview of its features by Gleb Bahmutov.

If you're looking for some books on software testing, Oleksandr Romanov describes his personal selection.

In this 7-minute video, Pramod Dutta shares honest examples of what it takes to be a QA Lead based on his experience.

This is a great discussion between Roman Sandler and Gleb Bahmutov on the test pyramid and other test strategy options.

Testing in production... and again! 😂

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