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

Betting in Testing

“I’ve completed my testing of this feature, and I think it's ready to ship” “Are you willing to bet on that?” No, Don't worry, I’m not going to list various ways you could test the feature better or things you might have forgotten. Instead, I recommend you to ask yourself that question next time you believe you are finished.  Why? It might cause you to analyse your belief more critically. We arrive at a decision usually by means of a mixture of emotion, convention and reason. Considering the question of whether the feature and the app are good enough as a bet is likely to make you use a more evidence-based approach. Testing is gambling with your time to find information about the app. Why do I think I am done here? Would I bet money/reputation on it? I have a checklist stuck to one of my screens, that I read and contemplate when I get to this point. When you have considered the options, you may decide to check some more things or ship the app

XSS and Open Redirect on Telegraph.co.uk Authentication pages

I recently found a couple of security issues with the Telegraph.co.uk website. The site contained an Open redirect as well as an XSS vulnerability. These issues were in the authentication section of the website, https://auth.telegraph.co.uk/ . The flaws could provide an easy means to phish customer details and passwords from unsuspecting users. I informed the telegraph's technical management, as part of a responsible disclosure process. The telegraph management forwarded the issue report and thanked me the same day. (12th May 2014) The fix went live between the 11th and 14th of July, 2 months after the issue was reported. The details: The code served via auth.telegraph.co.uk appeared to have 2 vulnerabilities, an open redirect and a reflected Cross Site Scripting (XSS) vulnerability. Both types of vulnerabilty are in the OWASP Top 10 and can be used to manipulate and phish users of a website. As well has potentially hijack a user's session. Compromised URLs, that exp

DevOps and Software Testing.

Most of my recent work has been with DevOps teams. While in one sense DevOps is another evolution in software development. It also introduces some new skill requirements and responsibilities into the daily routine of a tester. These diagrams tend to confuse people, hence the video... I've created a short video to highlight some of these changes and the opportunities they bring. It's not an exhaustive view of DevOps but it gives a highlight of what you could be working with. While DevOps isn't a panacea to our software development problems, I have found that empowering teams with the ability to build and use the tools they need, can rapidly improve team morale and productivity.