Issue 145

COMMENT

Welcome to the 145th issue!

While browsing Reddit this week, an interesting thread caught my eye:

Do you enjoy your QA job?

I went through the comments and realised that people like it for various reasons.

And this made me reflect on why I enjoy what I've been doing for nearly 10 years now.

So here are the three most important and constant factors to me (apart from the salary):

Diversity. And I mean both people as well as work. I like the idea of a tester's role as a glue between different functions. For example, one day I'm working with product managers, the other day with developers, and another day with customers.
Challenge. Software testing isn't easy. There's a lot of uncertainty and subjectivity to it that makes participation in every project a challenging experience. But thanks to that, I can't get bored of it.
Impact. It works both ways — I can impact the quality and delivery of critical projects as well as help my colleagues become better testers. And wearing many hats naturally creates more opportunities for that.

Now, over to you. What do you enjoy the most about being a software tester?

Happy testing! 😊

NEWS

Built-In Quality: A Reality Check

What practices can help teams create quality products? Venkat Ramakrishnan gives a good overview.

In relation to that, James Thomas wrote a thought-provoking article about Satisfying the Requirements.

GitLab Organization for Quality & Velocity

Curious about how GitLab's quality practices? Antoine Craske wrote a thorough overview explaining each one of them.

You may also want to learn from Bas van Laarhoven about How To Set Up An Easy Agile Testing Process To Keep The Bugs away.

Reviewing Capgemini's "World Quality Report 2022-23"

Quite a few companies do annual surveys about software testing and quality-related matters. Here's an honest analysis of one of them by Lee Hawkins.

Software Testers Survival Guide — How to get through an economic downturn as a tester

In a time of slowdown and layoffs, such pieces of advice from Keith Klain can be especially helpful.

And finally, Sam Connelly explains why it's worth Having multiple CVs.

The easily forgotten test cases

Team Merlin shares a helpful cheat sheet of common test cases for APIs and web apps.

It may also be worth knowing how to Estimate Time to Test.

The Multiverse of Testing

How many roles does a modern tester have? Quite a few as Sahil Puri explains using an interesting metaphor.

Speaking of roles, Joep Schuurkes asks: Agile tester or quality engineer, who’s to say?

AUTOMATION

End-to-End that's a true End-to-End

Ryan Craven reminds us what end-to-end really means and how we can improve our tests to meet such coverage.

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

Practical tips to writing clean code for test automation

In this thorough article, Rex Jones II shows examples of clean code practices that can help you write maintainable tests.

On top of that, Gleb Bahmutov shares some Tips And Tricks For Writing Fast And Maintainable Front-End Tests with Cypress.

What is the purpose of automated testing?

This is one of the fundamental questions that we may often forget to ask. So it's interesting to see different perspectives and opinions shared here.

Your performance tests are smelly!

There are various ways of designing and implementing performance tests. Eldad Uzman gives some hints on what to be mindful of.

Also, you might be interested in Justin Bailey's Deep Dive Into K6 Performance Testing Tool For Automation Testing.

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

AND...

Closing a sprint... 🤣

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. ☕️

Issue 145 November 14th 2022

COMMENT

Sponsored Link

Black Friday is coming! Will your site be ready?