Arkisto: August 2011



Elonmerkki 2011 – Communicate with Style!

23. Augustta, 2011 | Kirjoittaja: Antti Niittyviita

Softwaretesting.fi goes offroad this week! I happen to go and visit a design- and communication megaevent, Elonmerkki. At the same time, I become an author, thanks to Katleena Kortesuo’s idea! I can barely contain my anticipation!

Elonmerkki is an event held in Marina Congress Center on 25th August 2011 with a slogan that gets translated to “Communicate with style”

Elonmerkki 2011’s stage will be visited by at least the following people: Dean Helena Hyvönen from the Aalto university of Art and Design, CEO Laura Lares from Kalevala Koru, senior innovation activist Anssi Tuulenmäki from Aalto university’s school of science, graphical designer Pekka Loiri, design director Markus Frey from Kauppalehti and CEO Vertti Kivi from Dsign. At the end of the day, marketing- and brand leader Peter Vesterbacka from Rovio talks about Angry Bird’s world domination tour.

So, a lot of really heavy stuff to digest, but why would you care about it?

Well. Everything has to do with my foolish decision to sign a paper, which binds me to write 7 blog texts from the topics discussed during that day. The texts will be published in our testing blog’s category Elonmerkki.

Dear testing guru. Now if ever you will have a good chance to take a closer look at the secrets of communication and branding. Now if ever is a good time to learn about sharing your own professionality with other people!

Trivial Amount of Test Cases

22. Augustta, 2011 | Kirjoittaja: Antti Niittyviita

I say that you can test any software with one test case! The test case does not even need to be complex. The question is only about the tester understanding what is written and doing the job. I reveal a secret. I will not demonstrate a test case I planned for the web service Twitter.com a mere moment ago.

Step 1: Test Twitter.com

Expected result 1: Twitter.com works

Nothing mysterious there. With one test case we get to test the entire system and we can of course also measure the system’s functionality reliably. Right?

Any project leader who has any knowledge of testing would of course find my logic faulty. You simply cannot measure any system with one test case. You don’t even get any metrics from that.

Well, that’s the way it is. The question is, how many test cases do we need then, to get good metrics? How easy should it be to pass the test barrier for the metrics to be reliable? I for one do not know the answer. I am pretty sure that the project leader does not know either.

You can test this yourself. Write one test case like the above about a freely picked target. Then start turning your test sieve’s resolution controller. Split each test case into two new ones and see how far you get before you start to get frustrated.

The number of test cases is an useless meter. Toss it away while you still can!

Inquisitive Child

9. Augustta, 2011 | Kirjoittaja: Antti Niittyviita

I took the bus to work this morning and happened to witness a discussion between a boy of around three years of age and presumably his grandmother. I gathered that the child had reached the inquisitive age, since he was full of questions during those fifteen minutes of travel time.

Is this our stop? – Not yet

What is our stop? -Toripakka

When are we there? -Maybe after around ten minutes?

What does the stop look like? –Well, it has a roof and probably a lot of people waiting

Why do we ride this bus? –It is a handy way to get to the city

What do we do when we have reached there? –We go to the park

Why do we go to the park? –To play and eat our packed lunch. Don’t you think it would be fun?

It sure is! I guess we’re there, I can see the roof and people! –Well, so we are! Now we can get off

To a bystander, the questions seemed a bit funny. On the other hand, how else would a child learn anything? The little person built his understanding through questions, it is clear that riding a bus had not yet become familiar to him. The questions are essential for evaluating upcoming events.

In the same way, it would be good for a tester to ensure about why something is done and how long it takes. In addition, it is good to think about the specifications for when you know a release to be worth going public. Finally, it is good to think about what to do after launching a release. This way, the direction will stay clear in your mind.

If you do not know, do not presume. Unleash your inner inquisitive child and observe the world through the eyes of a three-year-old. Ask, ensure and doubt. You are sure to find new perspective for testing.