Po Po Po Po POWER Testing

One our first employees is called Franklyn. He is from the Dominican Republic and started his testing carreer a bit more then 5 years ago with TestABil. Franklyn has been an boxer in his youth and also has a pretty good hit for baseball. He still is a baseball fanatic.

Over the years in various projects in TestABil he has created a very good sense for defects. He can smell them from a distance. Is he the most organised tester, no. Is he a automation crack, no. Franky is getting bored very quick if he has not shouted DEFECTAZO at least every 2 hours. He moves in his chair, clicks on back and forward buttons, refreshes the screen… he will get really nervous. He needs to put all his power on his test to push the bugs to light. In our Mantis defect metrics he is the absolute number one.

A short time ago we started a testing project for a new online database. In a few weeks time my team was very busy with writing and executing test cases. But… the number of defects was a bit low. The customer (at 800 km distance) was wondering why there were so few defects.

I explained that we were doing a full test and that we had a lot of test cases to do. But, as the customer wanted to know quickly if the provider had delivered a ´bug´ free product we had to do something. I proposed the customer that we could do a one day ´bug hunt´ without executing “formal”  testcases. They agreed as they quickly wanted to see some bugs.

I called in Franklyn for one day (he is in another project) to help.

The result:

  • totally 78 bugs reported (70% severity major&crash), with step by step descriptions.
  • We identified new possible test cases
  • The team learned some test techniques in practice
  • The customer happy because we could warn them on time.

The bug winner: Franklyn with 38 (among which 70% severity major & crash). So we heard more then 25 times “DEFECTAZO”  in one day!

The rest of the team was impressed and also learned some tricks from him.

They now call him the PO-PO-PO-PO POWER TESTER.

What kind of test is this: exploratory, well no, although we explored a lot we were to focussed on bugs, also it is done when you are already doing structured testing, we really could confirm that the reported bugs were bugs. Is it a bug hunt, well maybe, although I like the following term: POWER TESTING, a one day test execution using powerful test techniques to bring to light high severity bugs.

I believe this test is ideal for web sites that already are on the web. Or projects that have decreasing defect metrics. Just to see…what  you cannot see…

Power Testing

Advertisements

3 Responses to “Po Po Po Po POWER Testing”

  1. Ed Says:

    Hi Anko,

    Can you elaborate your powerful test these techniques, because that seems to be the essence of your POWER TESTING approach. Without further explanation it is difficult to interpret.

    Ed

  2. Ed Says:

    Hi Anko,

    In your article you wrote :”a one day test execution using powerful test techniques to bring to light high severity bugs.” I was wondering what (combination of) test techniques you used to find more high severity defects than usual.

    Regards,
    Ed

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


%d bloggers like this: