Welcome to the 207th issue!

After surveying 47 tech professionals about testing practices, Gergely Orosz described the state of Quality Assurance Across the Tech Industry.

Although the free article unveils only a third of the full content, it offers valuable insights into:

• how the traditional QA role is transforming,
• how small, mid and big companies test,
• a case of Indeed that fired all QA.

One of the intriguing questions it raises is whether the no-QA movement is a temporary change or a trend that will amplify in the future.

We're yet to see.

For now, the best we can do is to keep investing in growing our skills. And I truly hope this newsletter helps you with that.

So, happy testing! 🙂

Dawid Dylowicz

Irfan Mujagić tells us why it's important to test for system robustness during components' failures and advises on how to achieve that.

Bob Salmon shares a short analogy explaining why defining something as a bug depends on the context, perspective and requirements.

Being the sole tester in a company is not an easy gig. Yulia Sharabi has some good pieces of advice on what to do in such a situation.

Also, Maria Golubeva describes a few Things I wish I hadn't done as a Junior QA Engineer.

In this interesting overview, Pablo Vergara shares how using system analysis helped him become a better tester.

Moreover, Lidia Barkanova shares a wonderful comparison of Testing As An Art.

Team Merlin points out that reliance on third-party resources, such as plugins and libraries, then it naturally carries security risks that should be tracked and managed.

Furthermore, Callum Akehurst-Ryan rightly explains why 100% Tested Is Not 100% Covered.

It's hard to disagree with the arguments brought up by Łukasz Makuch explaining why testing should be implemented as part of development. Handy if you need to explain the importance of testing to your team.

If your end-to-end tests are complex, flaky and take a long time to execute, you probably should consider breaking them down into smaller tests, as Bas Dijkstra illustrates with examples.

Similarly, Shyamal Raju advocates for Micro Tests, Macro Impacts: The Benefits of Switching to Atomic Testing.

Despite being the most popular design pattern in test automation, the Page Object Model is not always the ultimate solution. Sebastian Viquez explains why, using Cypress tests as an example.

Muhammet Topcu continues the thorough series of articles on setting up a test framework for web apps using Ruby and Selenium.

Curious how Reddit tackled its flaky tests? Kudos to Abinodh Thomas for sharing this comprehensive overview.

Have you ever delayed doing test automation because the project is too fresh and the code changes often? Gregory Paciga explains why it's not a good way to go.

Also, there's some good advice from Joep Schuurkes on Tackling test automation in a new language.

Wondering how the most popular continuous integration providers compare? Rodrigo Matola tested each of them out and shared his insights.

If you're still on the older version of Appium and want to switch to the latest version, Elizabeth Grillo wrote a handy guide that can help you with the migration.

After using dozens of other test runners for Node apps, such as Jasmine, Jest and Vitest, we can finally enjoy a fully built-in NodeJS solution. Here's Gemma Black telling us more about it.

Curious about testing APIs with Cypress? Gleb Bahmutov wrote a comprehensive guide explaining everything in detail with examples.

It's important to understand what browsers are used the most and on what devices. Max Kombarov shares the results of his analysis.

I also recommend checking out Statcounter, as I mentioned in one of the past issues.

Ah, the pull requests... 🤣

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