Welcome to the 14th issue of Software Testing Weekly!

One thing from me this week is an absolute gem that I've stumbled upon. Ever wondered how software is tested in particular companies? Apple, NASA, Grab — you name it. Well, just check out this amazing collection curated by Abhijeet Vaikar. Hats off!

Happy Easter everyone! 🐰

Dawid Dylowicz

I really enjoyed Jason Arbon's honest take on the future of testing in terms of what, where, when, why and how. Good food for thought!

Each of us has a unique story of starting in software testing. In my case, it wasn't a thoroughly planned in advance career path but rather an opportunity that showed up by chance. I took it, I loved it, and I stayed. Now I enjoy learning about other people's stories — like this one by Aline Lanckneus who recently got into software testing. What is your story?

If you don't understand where the bugs come from, you're less likely to prevent them from happening again. I've noted down some of the Root Cause Analysis techniques that Alona and her team used to reduce the number of defects by impressive 37%.

However, you can't prevent all bugs from happening because they are the inevitable part of software development. Luckily, you can make everyone's life easier if you report the bugs effectively. Andrew Knight provides some solid pieces of advice on how to do it well.

Property-based testing is a great way to reuse one test with various inputs. In this amazing guide, Carolyn Stransky and Fredrik Fornwall share pretty much everything we need to know about this technique, including code examples and libraries to use. Thanks for that!

Once I overheard that if you want to measure ROI of testing — simply stop testing. Omar Galeano took a more mathematical approach trying to define the return of investment of testing. Not so trivial, as you may guess, but really helpful!

PS. It's a premium article on Medium, so if you can't access it, simply open the link in a private tab.

When you approach a new project to test, it's good to start with some solid principles. Dennis Martinez shares three universal "dos and don'ts" of test automation that are well worth keeping in mind.

It's Easter time, but why not talk about Christmas! This time Viktor Slavchev shares his rather bold point of view on making CI builds green and cooperation between testers and developers. Hard not to agree!

StaleElementReferenceException is something I didn't entirely understand in Selenium, until now. Thanks, Babu Manickam, for explaining it in a simple way!

I haven't had a chance to try Robot Framework yet but I have no excuse now as Er Jasmine Baral explained the framework well in this guide, including how to set up and run the tests with page objects and BDD baked in. __

Trying to fix an issue be like... 😂