BLOG
TESTING

The Relentless Ticking of Time

Tick. Tock.

~ Written By Andrew Fullen

Tick. Tock. Tick. Tock.

Do you hear that?

Tick. Tock.

It’s the clock ticking down the time left on your project.

Tick. Tock.

Unless you are going to shift your completion date to the right, then you are not-so slowly eating up your testing time.

Tick. Tock.

That clock’s annoying, isn’t it?

Tick. Tock.

That’s another test your could have been running that you’ve run out of time for. So what could you have done to reduce the time pressure that you are facing?

Tick. Tock. Ti……

Automation is often suggested as a good way of saving time and improving quality. In the World Quality Report the respondents put the figure of automated test cases at a fraction over 45%. Hey that’s good,

Tick. Tock.

isn’t it?

Tick. Tick. Tick

Automation has been around for quite a while. Computers were invented and 5 minutes later the first programmers figured out a way of saving sometime to get the computer to do something for them while they had a cup of tea.

Tick. Tock.

But 45% isn’t that much is it? What next? 50%? 51%?

Tick. Tock.

How about 100%? That’s what I’m aiming for. To do that automation has to be right at the start of any project. As the requirements are being designed then the questions you need to be asking  are 1. Can we build it? 2. Does it give you value? 3. How do we automate it? I’m not saying how do we test it. If we can code it, and it gives value then it can be tested. But the automated test case needs to be there right at the very front. When the code comes in, so does the test.

Tick. Tock. Time for tea.

Andrew Fullen
Andrew Fullen
Managing Consultant / Sogeti Studio Delivery Manager
+44 0 20 7014 8900
todo todo
contact us
  • Sogeti UK
    Sogeti UK
    Make an enquiry
    0330 588 8200