Why Every Software Tester Should Watch Pulp Fiction – Neotys Testing Roundup

1. Why Every Software Tester Should Watch Pulp Fiction

This week, we’d like to start off our roundup with a fun, unique read from StickyMinds author Laszlo Szegedi. If you’ve never seen the 1994 modern classic Pulp Fiction, carve out some time and stream it on Netflix. Of course, you’ll notice the salty language and objectionable content, but can you pinpoint any plot points or film techniques that mirror your experiences in software testing?

According to Szegedi, the movie’s eclectic dialogue, groundbreaking cinematography, and dramatic flair actually provide good inspiration to talk about a few things every tester has probably experienced in his or her career. For a look at his clever comparisons, read the full article here.

2. When Do You Stop Testing?

Time to address some misconceptions about the correct time to end testing efforts. Now, testers may think they’re done testing when there are no more bugs left and the product can be shipped. However, author Yegor Bugayenko states that thinking like this is fundamentally wrong.

Bugayenko references The Art of Software Testing, a book written by Glenford Myers that explains this industry viewpoint. This article summarizes many of the book’s main points while taking a deeper dive into the logic behind them. Bugayenko then concludes his post by stating the only valid criteria for exiting a testing process. Find out what it is here.

3. A Tester’s Guide to Dealing with Scrummerfall

We can all agree, life would be a bit simpler if everything was black and white. Unfortunately, we encounter grey areas quite often and sometimes these areas can trip us up, distracting us from our goals. If you’re a tester on an Agile team, you may have experienced a grey area known as “Scrummerfall,”—a cross between Scrum and waterfall.

There are several indications that you’re working in Scrummerfall—sprint planning includes larger tasks that take nearly an entire sprint to complete, there really isn’t any collaboration between testers and developers, and too much work in progress exists during each sprint. If you find yourself in a Scrummerfall situation, this article should help. It lists a few different approaches testers can use to plan for, and against, Scrummerfall. Take a look!

4. Discussion: Common Errors as a New Tester

As a new tester, I’m sure it would have been helpful to have received a guide with all of the common problems new testers face in their careers. If you were lucky enough to receive information like this when you started out in testing, it’s time to pay it forward.

New testers are entering the industry every day, and these individuals are simply striving to adapt to their role while figuring out how it works. These testers will undoubtedly benefit from insight into the errors new testers seem to make all the time, so contribute to this Test Huddle Forum conversation and provide your thoughts on the subject here.

Leave a Reply

Your email address will not be published. Required fields are marked *