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

Can Gen-AI understand Payments?

When it comes to rolling out updates to large complex banking systems, things can get messy quickly. Of course, the holy grail is to have each subsystem work well independently and to do some form of Pact or contract testing – reducing the complex and painful integration work. But nonetheless – at some point you are going to need to see if the dog and the pony can do their show together – and its generally better to do that in a way that doesn’t make millions of pounds of transactions fail – in a highly public manner, in production.  (This post is based on my recent lightning talk at  PyData London ) For the last few years, I’ve worked in the world of high value, real time and cross border payments, And one of the sticking points in bank [software] integration is message generation. A lot of time is spent dreaming up and creating those messages, then maintaining what you have just built. The world of payments runs on messages, these days they are often XML messages – and they ...

What possible use could Gen AI be to me? (Part 1)

There’s a great scene in the Simpsons where the Monorail salesman comes to town and everyone (except Lisa of course) is quickly entranced by Monorail fever… He has an answer for every question and guess what? The Monorail will solve all the problems… somehow. The hype around Generative AI can seem a bit like that, and like Monorail-guy the sales-guy’s assure you Gen AI will solve all your problems - but can be pretty vague on the “how” part of the answer. So I’m going to provide a few short guides into how Generative (& other forms of AI) Artificial Intelligence can help you and your team. I’ll pitch the technical level differently for each one, and we’ll start with something fairly not technical: Custom Chatbots. ChatBots these days have evolved from the crude web sales tools of ten years ago, designed to hoover up leads for the sales team. They can now provide informative answers to questions based on documents or websites. If we take the most famous: Chat GPT 4. If we ignore the...

Don't be a Vogon, make it easy to access your test data!

 The beginning of the hitch-hikers guide to the galaxy leads with an alien ship about to destroy the Earth, and the aliens saying we (mankind) should have been more prepared – as a notice had been on display quite clearly – on Alpha Centauri the nearby star system, for 50 years. Seriously, people - what are you moaning about – get with the program?  The book then continues with the theme of bureaucratic rigidity and shallow interpretations of limited data. E.g. The titular guide’s description of the entire Earth is one word: “Harmless”, but after extensive review the new edition will state: “Mostly harmless”. Arthur Dent argues with the Vogons about poor data access This rings true for many software testing work, especially those with externally developed software, be that external to the team or external to the company. The same approaches that teams use to develop their locally developed usually don’t work well. This leads to a large suite of shallow tests that are usually h...