Formal Test Design Technique – Neotys Testing Roundup

1. The Advantages of Utilizing Formal Test Design Techniques

There are two kinds of people in this world – tea drinkers and coffee drinkers, PC users and Mac users, those who believe in the use of formal test design techniques and those who believe those same techniques cause rigid thinking and limit creativity. This post address the latter.

Author Dale Perry speaks for the value of these techniques as a basis for formal analysis and design as well as for creative thinking. His article explores the two main advantages of both formal black and white box techniques while encouraging testers to attain, at the very least, a general knowledge of this practice. Read on…

2. The Definitive Guide to Crowdsourced Testing (for Testers and Companies)

In recent years, crowdsourced testing has gained popularity as development teams look to gain real insight into product quality. This concept not only provides testers with a way to collect additional feedback, but it can also act as a secondary source of income for many testers. This Definitive Guide is designed for companies interested in crowdsourced testing and testers who may want to dabble in the practice.

Dive right in for a detailed look at best practices, procedures, phases, benefits, limitations, etc. of crowdsourced testing. Read the full article.

3. Are You Ready for Go-Live? Eight Essential Questions

As a tester, it’s difficult to escape external pressures. Looming release dates and other factors can weigh heavily on software testers during any given project, however, it’s important to understand the repercussions of rushed actions.

As real and daunting as scheduling pressures can be, they have to be balanced with the consequences of a potentially disastrous premature go-live. Don’t let all the reasons a system simply “must” be implemented by a target date overwhelm compelling evidence that it is not ready. Consider the eight questions outlined in this article first.

4. What is a Tester?

When it comes to software testing, it’s easy for outsiders to simply think, “Testers just break stuff all day.” This sentiment is shared by a junior tester who penned some of the issues she’s encountering in describing her work.

This article response from Michael Bolton addresses this widely held view and presents a list of metaphors he uses to jumpstart conversations about what exactly a tester does.
Take a look!

Leave a Reply

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