Over a million developers have joined DZone.

Why Do We Test?

Do we test because of Quality, or is there a more primitive brain need that drives us to test?

· DevOps Zone

The DevOps zone is brought to you in partnership with Sonatype Nexus. The Nexus suite helps scale your DevOps delivery with continuous component intelligence integrated into development tools, including Eclipse, IntelliJ, Jenkins, Bamboo, SonarQube and more. Schedule a demo today

I was listening to a great podcast series by Jeffrey Kluger on the topic of Space called It’s Your Universe.

it's your universe- TIME

During the first episode of the series he explained that, even though the formal reasons why NASA invests billions of dollars in space exploration is in order to advance humanity, the real reason is that the people at NASA explore Space is simply because it’s there.

As he said it:

The whole point of the Journey,
is the Journey!

As I heard him explain this logical but fascinating point, I could not help but think if there is a parallelism to our work, and to the reasons behind software testing.

Why Do We Test?

I asked some people on Twitter and Facebook the other day and I got some answers worth mentioning.

For example, the people who test in order to ensure the product is released at high quality.  Or those who test to “to be part of making a better world, to help people” – this is a really good reason if you ask me!  We can even go as far as mentioning those who test because no one else will do it, or at least no one else will do it right.

But I am interested here in the deeper question: Do we test because of quality, or is there a more primitive need?

Just as Astronauts and Cosmonauts enroll into their “profession” because they have the bug of exploring “the final frontier”, maybe many testers find this type of satisfaction from discovering that “extremely hard-to-find bug” before the product is released to millions of users!?

OK, OK.proud to be a tester No need to get agitated here! I know I am comparing people who fly on top of about 2,000 tons of fuel for a living to guys like you and me, where the biggest risks we take is whether to order the Hamburger or Beef Burrito for lunch, but you see where I am going here!

We Are Here for the Value, Not for the Bugs, But…

I will be the first person to come forward and say that the job of the tester is not to find the bugs, but to provide stakeholders with visibility into the product to make their decisions… yada yada yada!

But as only another tester will understand, there is a mindgasm related to finding those bugs that you are sure no one else would find in a thousand years, and that by finding them you just saved your company thousands or even millions of dollars!

We don’t do it because of the glory. After all, what glory is there in finding the issues that should not have been there from the start. We do it for the challenge!

Anyone who has ever completed a “very hard” personal challenge, such as to quitting smoking, graduating from College, losing 5 Kg, or finishing a 10K race will know. There is a great level of personal satisfaction that comes from achieving a hard and demanding task that required the skills and perseverance that only you could provide.

This is the same feeling we testers get from discovering those important and hard-to-find bugs.

Next Time Someone Asks, You Do It Because You Like It!

The bottom line is that if you feel something like the way I described in these preceding lines, it means that you are into testing because you derive satisfaction from it.

There is no shame in accepting this!

And so, next time someone asks “Why are you a tester?” you can simply answer him or her that you do it because you like it, and you enjoy the challenges that testing provides you as part of your work!

Train Testers to Enjoy Their Achievements!

No less important is the need for us, experienced testers and test managers, to help junior and beginner testers to enjoy their achievements.

motivationJust like when you reinforce a kid by celebrating their first steps, or their good grades, or their sport accomplishments; in just this same way we need to celebrate the good bug findings of our testers in order to reinforce their feelings of achievement!

As trivial as this may sound to some of you, I have been in organizations where bugs were kept as quiet as possible so as not to hurt the feelings of the programmers.  And all this is good and fine, but WHAT ABOUT THE TESTERS?!?!

We need to look for a smart way of celebrating the great “saves” of our testers without vilifying the developers.

Think about this…

Why Do YOU Test?

Do you have any story of a Fantastic Discovery or Great Achievement in testing that gave you great satisfaction?

I would like to ask you to share it, so that other testers (both beginners and experienced testers) can learn from it and get more motivation to exceed at their jobs!

The DevOps zone is brought to you in partnership with Sonatype Nexus. Use the Nexus Suite to automate your software supply chain and ensure you're using the highest quality open source components at every step of the development lifecycle. Get Nexus today

bugs,bug,test driven

Published at DZone with permission of Joel Montvelisky, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}