Skip to main content

Saving Time?

For those of you that don't know, I'm somewhat of an amateur horologist. I love clocks, watches and all sorts of time and date keeping gadgets. To feed my passion I've decided to invest in my own custom made timepiece. This device will be my first custom made high value item, in what I hope will one day be a great collection.

To ensure I get what I want, I've taken some time and documented the following requirements for my new clock. They list what I want from the timepiece, and also what I don't want or need. Have a read through, and hopefully you'll see what it is I'm after.

A new clock should be developed for my new home in London.

The clock will need to:
- Display the time.
- Display in roman numerals and modern 'arabic' numerals.
- Be accurate enough for household use - approx' to with in a few minutes.
- Be ornamental - preferably with a intricately styled clock face.
- Have a traditional square brass clock face
- Be constructed from traditional clock materials like brass.
- Be water resistant - as it may be used in the garden.
- Resilient to wind - as it may be used in the garden.
- Not have a chime, bell, cuckoo or another form of 'noisy' time indicator.
- No special case or stand is required.

Now as a tester, I keep hearing that that we should all be writing up our test cases in advance. Sounds sensible, and assuming I have some documented requirements; I can get 'ahead of the game' and write my tests up front.

Ok, I've been bitten before. I'm not just going to write tests that check the system one way for each requirement. For example, 'Be water resistant', I'm not just going to splash a bit of water on the clock face. I'm going to splash water from at least three sides, and at least four different intensities of water.

I'll do that for each requirement. Creating a comprehensive suite of tests that I can use for testing the device when I receive it. I can also use them as a regression 'test pack' anytime in the future, without having to 'think'.

Now, lets jump forward in time. It's now the evening of 24th December 2011. My clock is sitting on the table, near the back door of my house. I've been impressed with my clock, I don't use it every day but when I have - It has worked well. But I look at it now - and I just can't figure out the time - something must be broken.

Take a look back at your tests - could they find the bug?

You can find a picture of the clock here. And a clue to why it isn't working here.

Comments

  1. Is it because it's dark and / or it's in Winter? Tried not to look at the clue first but figured that out from the date in which you were using it. It would work perfectly in the Summer months when the Sun is high in the sky, but in the Winter months the time may be completely off as the Sun is quite low.

    Good little exercise! I enjoyed reading this post!

    Adam
    http://testing.gobanana.co.uk

    ReplyDelete

Post a Comment

Popular posts from this blog

Why you might need testers

I remember teaching my son to ride his bike. No, Strike that, Helping him to learn to ride his bike. It’s that way round – if we are honest – he was changing his brain so it could adapt to the mechanism and behaviour of the bike. I was just holding the bike, pushing and showering him with praise and tips.
If he fell, I didn’t and couldn’t change the way he was riding the bike. I suggested things, rubbed his sore knee and pointed out that he had just cycled more in that last attempt – than he had ever managed before - Son this is working, you’re getting it.
I had help of course, Gravity being one. When he lost balance, it hurt. Not a lot, but enough for his brain to get the feedback it needed to rewire a few neurons. If the mistakes were subtler, advice might help – try going faster – that will make the bike less wobbly. The excitement of going faster and better helped rewire a few more neurons.
When we have this sort of immediate feedback we learn quicker, we improve our game. When the f…

Thank you for finding the bug I missed.

Thank you to the colleague/customer/product owner, who found the bug I missed. That oversight, was (at least in part) my mistake. I've been thinking about what happened and what that means to me and my team.

I'm happy you told me about the issue you found, because you...

1) Opened my eyes to a situation I'd never have thought to investigate.

2) Gave me another item for my checklist of things to check in future.

3) Made me remember, that we are never done testing.

4) Are never sure if the application 'works' well enough.

5) Reminded me to explore more and build less.

6) To request that we may wish to assign more time to finding these issues.

7) Let me experience the hindsight bias, so that the edge-case now seems obvious!

Being a square keeps you from going around in circles.

After a weary few hours sorting through, re-running and manually double checking the "automated test" results, the team decide they need to "run the tests again!", that's a problem to the team. Why? because they are too slow. The 'test' runs take too long and they won't have the results until tomorrow.
How does our team intend to fix the problem? ... make the tests run faster. Maybe use a new framework, get better hardware or some other cool trick. The team get busy, update the test tools and soon find them selves in a similar position. Now of course they need to rewrite them in language X or using a new [A-Z]+DD methodology. I can't believe you are still using technology Z , Luddites!
Updating your tooling, and using a methodology appropriate to your context makes sense and should be factored into your workflow and estimates. But the above approach to solving the problem, starts with the wrong problem. As such, its not likely to find the right ans…