Arkisto: October 2011

What Should One get, when Shopping for Testing?

24. Octoberta, 2011 | Kirjoittaja: Antti Niittyviita

Last Friday we stopped during a coffee break to ponder tester’s work. While brainstorming, we decided to focus on which is the most important result of a tester’s work?

There are loads of answers for that, like there are loads of testers. Some think that the most important thing is to improve the quality. Some think that it is about producing metrics. Some claim that a tester builds up trust in the product’s quality. And some think that a tester destroys trust in the product’s quality.

There were way too many answers while we brainstormed, so we decided to simplify the problem in the face of options.

If testing department’s budget is set to be painfully tight and you would have to cut expenses even further, what would you ultimately remain with?

  • Test specs and cases? Trashed.
  • Measuring test results? Trashed.
  • Test planning? Trashed.
  • Automation? Trashed.
  • Checking work? Trashed.
  • Test control systems? Trashed.

A pretty hefty slice of a tester’s daily work just got trashed in our table. But one thing remained. What do you think it was?

That’s right. Bugs remained. They tell you what is wrong with the software. They tell you why the paying end user might complain or be unhappy. They tell you what pitfalls to avoid when publishing. In all their simplicity they are

Things that Bug you

What if the next time around when you are shopping for testing, you only go for the concrete result? Only buy bughunting next time!

Plain as Day, but only to me

6. Octoberta, 2011 | Kirjoittaja: Antti Niittyviita

In September, I visited the Technology Entrepreneurship Days in Oulu. After the lunch on the first day, we moved over to the hall to prepare mentally for the afternoon’s speeches. I, being a keen participant, seated myself in the front row. Behind me sat a woman in a dress coat.

The hall, which had been rented from the city theatre for the seminar, was dark and the air conditioning worked like a charm. I thought the temperature was the right level of cool. The woman behind me must have not agreed with me, since she took her coat to cover her legs with it.

Did you get cold? I asked.

The woman nodded.

What a silly question. It must have been plain as day, when the air conditioning was running at such a level. I replied.

The man who sat on my right was not a testing guru, but still he managed to catch me having a bias.

How did you know she was cold? Maybe she just wanted to cover her beautiful legs with the coat?

Even though I am a mouthy fellow, that made me shut up. A professional tester should automatically try to discard any bias. Terms, such as ‘plain as day’ should be quickly seized in project meetings, since they are usually governed by the same rule:

Being plain as day to you does not make it plain as day to me.