Testing without requirements is like...

So - how to describe software testing... I don't mean the blind execution of pre-existing testcases, I mean the testing most of us do... Here's a piece of software, go figure out what "works" and what doesn't...

Sometimes you have requirements (probably a discussion for a different post), but more often than not you don't, so how do you test something, when you don't know what it's supposed to do?

To me, testing without requirements can be described like finding a lost puppy.

You are out for a walk and you find a puppy (you are using the software and stumble across an undocumented feature - sound familiar?).

You check the puppy for a collar, dog tags, tattoo (requirements, User stories, Use cases) and find nothing.

You look for lost pet signs, go online for lost pets in your area, call the humane society (check your issue tracking system).

All you have is a lost pet and no easy way to uncover it's owner.

Time to go on the offensive!  You ask your neighbors if they know who owns the puppy (check with developers to find information about why it was developed). You post found pet signs in the neighborhood and online - you describe the colour and size of the puppy and hope!

You get a phone call - asking you the puppy's breed, gender, age, name - all things you cannot answer. This puppy didn't come with a spec sheet.

And people come and call "Here spot!" to see if the puppy will answer.

And someone comes and says - yes, this IS their puppy. How do you know? It's like asking your product owner if the feature is exactly what they wanted.  It might not be exactly what they were expecting when they started out, but they are willing to take it home and nurture it into a full size dog :)

New Perspective on Promoting Bug Advocacy

So I was a little saddened (and annoyed!) this week to find some of my team had defects / bugs / tickets / issues lingering and lingering and lingering.  So I thought I'd liven up the Bug Advocacy chat :)

I wondered if by calling it a bug we are creating the image of something that is creepy and unwanted and promoting the notion that these thing needs to be gotten rid of one way or another as quickly as possible. Allowing us to rely on the defect tracking system where we anonymously assign it to someone or leave a comment on the ticket and hope someone deals with it....

Queue today's team presentation:

Slide 1 - BIG cockroach

• When we talk about the bug we found in the software this is the type of image that springs to mind right? (team nods) And what do we want to do to bugs? "Squash it" (must have been riveting - already a response, but they think at this point they know where i'm going)

Slide 2 - Foot stomping on cockroach

• Exactly! We want to squash bug! But what i want you to think of when you find an issue is...

Slide 3 - 4 pictures of the cutest kittens on the first page of a Google image search of cute kittens

• A kitten!!!! And what do you do when you find a cute kitten?

Slide 4 - picture of kitten eating and picture of kitten dressed up

• You feed it, you take care of it, 

Slide 5 - picture of a girl hugging kitten

• You find the right owner for the kitten, who will look after the kitten and love it

Slide 6 - Lost kitten poster

• When i find a ticket with no owner, no comment no resolution it's like this - a lost kitten!

Slide 7 - Found kitten poster

•  Find those lost kittens! love them and care for them and find them an owner

So I've told my team I'm going to start asking them if they are caring for their kittens and making sure they don't get lost and giving them all the care and attention they deserve.

Hopefully I made a point - not sure where the idea for the cat chat came from, but I had fun and my team thinks I'm just a little bit crazier :).