20 Lessons Learned From 20 Years in Tech 💡

ISSUE 203 January 20th 2024

COMMENT

Welcome to the 203rd issue!

This time, I have something very insightful to share with you:

20 Lessons Learned From 20 Years in Tech: Part 1 and Part 2.

Written by Dennis Martinez who worked on a lot of projects as a consulting software engineer, including test automation.

Having experienced so much, I truly find his insights valuable.

Thanks for sharing, Dennis.

Happy testing! 🙂

Dawid Dylowicz

NEWS

21 Tips for Mastering the QA Career Path in 2024

In a three-part article, Bharat Varshney shares a lot of practical pieces of advice on how to become a better tester. Here you can read the second and the third parts.

Also, Filip Hric shares an interesting point of view on Testing as an entry gate to IT.

medium.com

QA and DevX — Architects of Happiness

Ivy Murphy explains how Developer Experience and Quality Assurance functions can support developers and contribute to overall team success.

However, as Karla Mieses points out: Let’s be honest, in some places, QAs are not respected by other team members.

medium.com

How to Determine OKRs for Software Quality Assurance

If you want to set objectives for your QA team, Putra Agung Pratama advises how to do that, using metrics and examples.

Speaking of metrics, Melissa Fisher came up with an interesting one: Test coverage — how about quality coverage?.

medium.com

Quality Assurance and Testing

Michael Bolton explains the common confusion in understanding the difference between quality assurance and testing

Similarly, James Thomas describes what it means (and doesn't mean) to Build Quality.

developsense.com

What To Do When You Need More Time To Test

How often do you find yourself running out of time to finish testing? Wayne Roseberry has some good advice on what to do in such a situation.

github.io

AUTOMATION

A Guide to Avoiding Anti-Patterns in Automation Testing

Facing challenges in test automation? Bharat Varshney points out what you might be doing wrong in terms of practices and testing patterns.

Bharat also shares valuable Advice for Clean, Modular, and Maintainable Test Code.

medium.com

Democratization of Test Automation — An ING Story

If you want to learn how a big bank approaches the test automation strategy, check out Ashish Ghosh's detailed overview.

Furthermore, Paul Grizzaffi uses a cooking metaphor to explain the potential problems with Multiple Automation Tools, Effort, and Messes.

medium.com

Social Testing at the Heart of Software

Have you heard of the concept of "sociable" tests? Rafael Miguel explains with examples what it means and when such practice might be useful.

Similarly, Gil Zilberfeld continues the series about Abstraction and Testing — The Other Side.

substack.com

Testing Too Difficult? Automate Your Integration Tests

Peter Flook describes in detail how to effectively use an integration testing strategy, especially around the data flows.

On that note, Roy Straub reminds us to Stop Testing Implementations.

medium.com

TOOLS

Best Test Reporting Tools in 2024

Looking for a free test reporting solution? Denis Peganov wrote a helpful overview of five selected tools for different scenarios.

medium.com

Easiest way to understand how Appium works

Sometimes you may take test tools for granted, but it's important to know how they really work. Here, Millan Kaul describes Appium in a simple way.

github.io

I made a free Chrome extension to write tests in any language

Someone on Reddit listened to the community's feedback and created Automize — a free, versatile Chrome extension for easy test implementation in many common test frameworks.

reddit.com

Playwright tips and tricks #2

Following the first part, Adrian Maciuc shares several more handy tips for writing tests with Playwright.

Also, in this handy guide, Jan Molak explains how to Extend Playwright Test with Serenity/JS and leverage the Screenplay Pattern.

martioli.com

Selenium vs … blog posts

There've been many articles comparing Selenium to other tools. So many, that David Burns — one of the key Selenium contributors — decided to officially address these claims.

selenium.dev