How is Exploratory Testing Different? – Neotys Testing Roundup

1. Are You In the Right Testing Job?

Two articles by Lou Adler published in May 2013, “There are only four jobs in the whole world – are you in the right one?” and “Rethinking work: Define the Actual job using the four work types”, created a watershed moment in my career. They made me sit up and realize that what I wanted to do, and what I was doing, were not the same thing, even though I had previously believed them to be so.

It took me months of introspection to understand what it was that floated my boat, and what I wanted out of my career.

Adler argues that there are only four types of job in the world: Thinkers, Builders, Improvers and Producers. He describes Thinkers as the strategists, the creators of new products and those that come up with big ideas and new ways of doing things, while the Builders take these and convert them into something tangible. Improvers, in turn, are those who make whatever has been built better. Lastly, the Producers deliver high-quality products and services to the customer.

Read the rest of the article here to determine what role are you playing.

2. How is Exploratory Testing Different?

Here’s a basic analogy for you to think of when presented with the idea of exploratory testing. You can cook pizza by following instructions or trying it out on your own. When you try it out on your own, you learn a lot more than merely following instructions. You don’t get a perfect pizza every time but once you get it, you would have made many mistakes. The next time you have to cook any food, you will be aware of the kind of mistakes you made with the pizza and in order to avoid more mistakes you ask a lot of questions.

However, you get a pizza faster when you follow instructions given to you. The goal is to not produce one pizza but thousands and if you need to keep following the instructions every time, the first pizza is faster but to produce thousands is slower. Accidentally if the instructions are wrong, you perfect the imperfect pizza. The next time someone asks you to cook pasta instead of pizza, you are ask for instructions, follow it and hope the instructions given to you are perfect.

To read more on exploratory testing click here.

3. Automated Test Nightmare, There and Back Again

In this interview, Wojciech Seliga shares from experience how complex it can be to deal with thousands of tests – unit, functional, integration, performance – for Atlassian JIRA and what they did to bring it under control.

Seliga runs a company he co-founded – Spartez – which partners with Atlassian on developing their core products. He is one of the leaders responsible for JIRA – one of the most popular issue trackers in the world. Wojciech has presented at Agile, AgileEE, Devoxx, GeeCon, Javarsovia/Confitura, 33rd Degree, Atlassian Summit, AtlasCamp, AgileByExample, XPDays, InfoSHARE and others.

4. How to Test Smarter: Explore More, Document Less

Test teams do a great job, and under difficult circumstances, thanks to budget crunches, compressed schedules, and concerns about security and usability.

Managers can help testers do a better job — a smarter job — by encouraging them to refocus some of their efforts away from test documentation and use that time instead to expand exploratory and ad-hoc testing.

One of the biggest problems facing IT organizations today is the compressed development cycle. Except for huge enterprise initiatives, almost nobody plans for cycles that are longer than a couple of months. Managers have to deal with short cycles and get quality software out the door. Coders have to write software faster. And testers have to accommodate new and changing functionality on ever-more-complex software without letting defects slip through undetected.

To read more on how to fix the compressed development cycle click here.

No Responses
  1. June 18, 2015

Leave a Reply

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