Issue 143

COMMENT

Welcome to the 143rd issue!

I enjoyed Girish Nair's summary of his Personal favourite Dilbert strips on Software Quality.

It's a perfect read if you want to be entertained and taught about testing at the same time.

Just right to start the weekend!

Happy testing! 🙂

NEWS

Documentation as a Quality Engineer

What importance does documentation have in software testing? And what are its types? Ryan Craven explains and shares a list of examples.

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

Don't Wait to Test — Go Explore!

Callum Akehurst-Ryan gives a handful of solid pieces of advice on how to be proactive in testing.

Furthermore, Callum gives a good overview of Technical Exploratory Testing — Using Dev Tools to Look under the Hood.

How to Maximize the Need for Testers

If you want to make the best out of the whole-team approach to testing, you should check Maaret Pyhäjärvi's warning about eight behaviours that you and your peers should avoid.

"Release Early, Release Often" Clarified

What can give you enough confidence to frequently deliver quality features to your customers? Zhimin Zhan's answer — short feedback loops with test automation.

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

QA KPIs

Someone on Reddit is looking for good quality metrics and people gave fair responses and suggestions.

Moreover, you may want to Use Ishikawa diagrams to improve quality as Mike Harris suggests.

AUTOMATION

Clean Code Architecture — Testing Considerations

You might have heard that quality is usually built into the product. Venkat Ramakrishnan brings up some valid points to explain how the Clean Code architecture increases testability.

You might also be interested in Venkat's related reads about the Requirements To Architecture and Architecture And Design.

Integration Testing via Contract Testing

Osman Ali Yardim writes about integration testing in microservices architecture and explains why contract testing is a reasonable way to do it. Supported by some examples in Pact.

Introducing Test Automation into your Project

Whether you're starting a new project or joining an existing one, you may want to listen to Radosław Landowski's advice on how to prepare for setting up test automation.

Also, some Test Automation Estimation techniques by Artur Shevchenko may come in handy.

Many Ways to Speed up Autotests

Andrey Enin shares great pieces of advice by showing 13 different ways of speeding up your tests with examples.

Moreover, Farhan Labib explains Test Automation Pyramid: How to Automate Test Effectively.

My latest automation testing strategy presumption (part 1)

In a series of articles, Arnon Ram gives a good overview of the test automation strategy based on the test pyramid. You can also read the second part and the third part.

TOOLS

Cypress vs Playwright — which JavaScript testing framework is better?

Józef Szymala does a deep comparison of two popular tools for testing web applications— Cypress and Playwright.

The power of Chrome DevTools Protocol

In a series of three (so far) articles, Germán Bisogno presents an insightful deep dive into the powerful Chrome DevTools Protocol.

Here you can read the second and the third parts.

BOOKS

5 Books For QA Engineers

If you're looking for some reading recommendations, Serhii Zabolennyi describes five great books for software testers.

Remembering Jerry: Quality Software Management Volume 4 — Anticipating Change

And finally, Markus Gärtner gives a detailed review of the last volume of this timeless book: Quality Software Management: Volume 4 — Anticipating Change.

VIDEOS

The Essence of Quality

In this 23-minute talk, Vitaly Sharovatov explains what quality and quality assurance are.

AND...

Enjoy your Friday... 😂

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 143 October 28th 2022