Monday, 26 January 2015

Keep on Running

10 runs into the year and I am surprised that:

  1. I am still running even though
  2. I was surprised with how incredibly unfit I was and that surprises me that
  3. I am actually getting better
The couch to 5k programme that I am following now has me running for 3 minutes.  180 seconds of running doesn't seem a lot, but 10 runs ago I couldn't go for 60 seconds so this is a massive improvement.  My last run detailed here: was the first run that I didn't do as a loop.  I ran from the Mountbatten centre through to cosham centre.  Although not the greatest distance, mentally it felt great to start in one place with a certain destination in mind.  At this point in my training plan this has been very helpful.

As I said when I started this I have been gathering statistics on every run and averaging them out over each week of the C25K programme.  I've decided to make this public in case anyone is interested.  Apart from the raw data I have learnt a few other things:

  1. Running with spectacles, in the rain, while getting too warm means you spend way too long trying to wipe away the rain and haze.
  2. Hills are hard, but only in one direction
  3. Never judge a run by your heart.  I can feel that a run has gone badly but the realz of the stats show that the run was awesome
  4. Running makes me feel so much better

Sunday, 4 January 2015

1st run of the year

After my new years resolutions I had to commit and actually run.  Naturally being a nerd this activity required tracking and monitoring. I spent quite a bit of time working out how to track my run, what I was going to listen to and where I was going to run.

Tracking my run.
I have started using run keeper on my phone for this task.  It tracks my run via built in GPS, gives me details of my progress every 5 mins and then saves all the stats of my run to the cloud.  I did consider a fitbit or jawbone device but this app was free and seems to do a fine job.  The app also allowed me to design routes online and then view them on my phone.  Quite handy to see where I was going to be running and how far that was in advance rather than just be running aimlessly.

What to listen to.
Instead of just picking a random running album I decided to use the NHS free couch to 5km podcasts.  Each one uses intervals of running and walking to build up stamina over a period of 9 weeks where hopefully I should be able to run 5km.  I transferred the podcasts to google play and then stream them to my phone.  Having someone tell you when to run and when to walk was quite helpful

So no need for any new toys.  Amy had already bought me some trainers and I have clothes that I can run in.  However since my phone was going to be my tracker and music player I invested in a karrimor arm band to house my phone and a pair of runners headphones.  Both were half price.  The headphone were very comfy and the arm band although too tight to fit on my upper arm kept my phone safe on my lower arm.

Wednesday, 31 December 2014

New years rulins

So it is another new year and as is customary I wanted to make some resolutions.  Reading my news feed on Twitter I saw a re-tweet from Lisa Crispin @lisacrispin pointing me toward this page which is a list of new years rulins from a musician called Woody Guthrie.  I have never heard of him before, but I liked his list and how through reading it I started to see a part of his life. So taking his lead (and his list) I have made my own heavily based on his, but adding my own thoughts and removing some of his less transferable entries.  I doubt this will be a year that unlike all others I keep to them all. But at least I can try.

Wishing everyone a happy and fulfilling 2015



Friday, 25 April 2014

Why No Test Cases

Why No Test Cases

The test team I lead do not use test cases.  We believe that testing is an active,  changing exercise and that rigid test cases does not support this rate of change.  I will give my arguments for not using test cases before explaining how we do plan and track our testing

What is a test case?

A test case defines a process that will show if the software you are testing displays a particular desirable attribute. It consists of 3 main parts:
  1. Starting condition
  2. Method
  3. End condition
And may have other parameters
  1. Priority
  2. Owner
  3. Status (open, in progress, blocked, closed)
  4. Weight
A low level test plan is a collection of these test cases for a particular module or capability of the software being tested.  The test plan is reviewed and approved by stakeholders rather than an individual review of each test case.

Reasons for change

Not all test cases are created equal

To paraphrase George Orwell "all test cases are created equally, but some test cases are more equal than others".   Each test case differs from others in terms of it’s:
  • Risk
  • Complexity
  • Duration
Tests when executed reduce the risk of faulty software being shipped to the customer.  From the customers perspective there are different levels of risk, some acceptable and some not.  The risk of a small input validation error within a utility program might be just annoying but other errors could cause a loss of money within a business or even loss of life for aviation or medical software.  Different tests mitigate different amounts of risk.

The complexity of a test case can also vary.  Modern software is rarely executed on it’s own and will likely have many integration points.  Configuring, executing and monitoring the software during the test can be a complex task.  Some simpler test cases though are a lot less complex.

Tests not only take time to execute but also can take considerable time to prepare the required test configurations and test harness to execute the test.  As well as time required by the tester to complete these tasks, longevity or workload tests can then take an extended period of elapsed time to execute the test. Validation of the test execution data once the test has executed will also add to the duration of the test case.

Some tests will have a natural ordering between them.  Quite often a test will build on top of previously run tests.  These tests will require the tests run earlier to pass in order for this test to be run.  

The above points show how varied and different a set of tests can be.  Defining these varied and many tests into a single unified ‘test case’ hides the differences between them.  Once in this form they are counted as if they were all identical in duration, risk and complexity. Boiling this complexity into a single test case template just hurts the testing.

Preparatory work

Any test case will require some degree of preparatory work before the 'actual test' can get underway.  This might be configuring automation, defining workloads or developing test harness to run the test.  Is this work part of the testing process or just necessary delay that has to be done before the real work starts.  Fellow testers seem to fall into one of two main schools of thought.  One group see prep work as a required evil, work that must be done but isn't part of the actual testing.  The other group are of the thinking that as soon as you start to interact with the new parts of the software, the process of testing has begun.  Either way how do you classify this work?  It doesn't fit into the test case template at all and yet the test cases are dependant on it being done.  When a team has 10 test cases remaining you don't know what work needs to be done to execute those tests?  They might need 3 days of prep work to be done first.

Once the prep work is completed you are left with a set of test cases and a period of time to complete them in.  This turns the test case into a metric and ...

Someone always wants to track them

There are x number of test cases left to do and y amount of time left to do it.  Simplistically this is modelled by a straight line graph.  The model assumes that each test can be executed in the same amount of time.
image (1).png

However as we have said before not all test cases are equal, so to assume that we can execute through them in a linear fashion is short sighted.  Also as test work progresses defects are raised which will require recreation and verification and this takes time, time that cannot then be spent on executing tests.  Responding to this the chart is often re-drawn as an s-curve like this one:


Progress is charted against the graph and teams either are congratulated or receive 'management focus' depending on the state of the chart.  This misses the point and it's largely the fault of the test cases.  Progress through a list of predefined tests means nothing.  For the progress to be meaningful you need to assume that the quality of the tests are high and that the tests mitigate the majority of the risk for the customer.  Even if you can make that assumption, progress through the test cases isn't enough to judge progress you also need to consider:
  • How many defects testers are finding.
  • The spread of defects across the product
  • What tests have actually been done yet (have we just done the easy ones)
  • what if we have completed 90% of the test cases and found no defects?
Without this additional information the complexity of testing is abandoned in favour of an overly simplified metric which is too narrow to be of any real use.

They don't react well to change

Testing is an exploratory sport, an experienced tester working through any set of test cases will question their approach based upon; progress through the test case, prior defects and often just a gut feeling.  Regardless of how much thought and effort is applied to the formulation of the test plan, the planned testing and the actual testing will be different.  This is because the tester is learning about the software and how it was implemented as they execute the tests.  A single test case might expose a bug which is part of a bug cluster within a piece of code.  To fully examine the area new test cases will be created and executed on the fly. This ad-hoc, off piste or exploratory testing should result in further test cases being written and added to the plan.  Adding extra tests often infuriates managers trying to track progress.  The new tests are driving further quality into the product and their value isn't in the testcase being written but in it being executed and the defects that they find.  

Test approaches such as scenario based, use-case or exploratory do not lend themselves to a formal test case report.  They often do not have a particular method or starting condition but instead tend to rely on experienced confident testers examining the product in the same way the intended customer would.  These approaches are better tracked using a time box or complexity rating like duration or story points.  

Test cases seem like a good idea.  However in reality they are too simple a model to use in practice.  A single test case can define the intent of a test but the model breaks when used to suggest progress or the quality of the product.

I explained this to a junior member of my team and drew parallels between some exploratory testing he wanted to achieve and a prototyping story that development were planning.  Both didn't have a clear plan of implementation but they did have allotted time and a focus on learning how to achieve their aim by 'working with the software'.

This was when an alternative became clear.  This is just software engineering.  Can't we measure software development and in the same way?  Would that makes things clearer

Whats the alternative

Test work is just engineering work

If you stop thinking about testing as being the execution of test cases and instead as another type of software engineering work then an alternative approach becomes obvious.  Testers still write code, examine specifications and solve problems in the same way as a developer.  We don't track developers by the number of changesets they produce so why not treat testers in the same way and use the same tracking artefacts that are used in development.

We now use test stories for our system. Test work.  No test cases in sight.

A Test Story is similar to a development story.  It outlines the objective of the work, priority, owner and complexity.  Except in a test story the objective could be more deconstructive than that of development story.  As a dev story is constructing something new, test are de-constructing it to reveal defects.

Test Stories can be planned for an iteration and split into multiple child tasks that describe each individual unit of work.  The test story is given an estimate of the time it might take, a priority of how important it is that this test is executed and a story point rating to describe how complex this test is to implement and execute

Handling defects

Defects found during the story executuon are linked to the work item to show the 'fruit' of that story.  Development and test stories can be associated to show the testing that will be applied to new capability

Defects that are found will often require recreating to provide further diagnostics and require verification once a fix is supplied. This work will need to be planned and committed to an iteration just like any other piece of work.  We have created queries to total the amount of time spent 'working' these defects.  This can help to explain delays in test progress as testers are working on defects.

Showing progress
We can now show our progress by explaining the work we have committed in an iteration and our burn down throughout the iteration.  Not using the simple metric of testcases focuses people to ask more interesting questions to determine the quality of the project:
  • What types of testing have we done?
  • What defects have we found?
  • How much time do we need to complete the high priority work
All more valid and useful than a single percentage of test case completion.

We have been using test stories as a replacement for test cases in the system test team for a few releases.  Using them has given us the following benefits:
  • The total amount of  test work that needs to be done including  prep, defect recreation and verification as well as actual testing.  We can plan our iterations a lot better.
  • Tracking is a lot easier as we can understand the duration as well as the complexity of the work rather than simple counting measures
  • We are starting to ask better questions about the state of the test project.

We still are not perfect.  We are still refining our process to ensure we estimate tasks better and ensure we don't fall into the trap of just counting test stories.  Overall we have seen an improvement in out efficiency.  Who needs test cases?  Not us!

Saturday, 25 January 2014

Playing with the scammers

Got a friend invite on facebook this morning from a Kelly Anderson.  Name was a bit familiar so I accepted the friend request and thought no more of it.  Later that evening I received a message from him on facebook messenger.  What follows is the conversation that we had with some contextual information from me.
  • Conversation started today
  • William Yates
    William Yates
    Hey. I got a friend request from you. Trying to figure out how I know you. Sorry I know that can sound rude
  • Kelly Anderson
    Kelly Anderson
    i don't really know you but i got through your profile in search of my old friend
    my name is General Kelly Anderson, i am from United State
    i lost my wife 6 years ago.. i have a son i just want you to know me much better as a friend
    its my pleasure to know you
  • Kelly Anderson
    Kelly Anderson
    i have a proposal for you
    i dont really know if i can trust you
    write to me pls its important
  • William Yates
    William Yates
    Sure what's up
  • Kelly Anderson
    Kelly Anderson
    i have been in Afghanistan 6 months now for peacekeeping
    and i have a son 11 years old in United State
    that is the only family i have
    we went for a mission some weeks back
    we found some cash which me and some four Generals shared
    but i have been looking for someone to trust
  • William Yates
    William Yates
    And you want to transfer it to my bank to get it back to the us
  • Kelly Anderson
    Kelly Anderson
    that is why i was searching for my old friend on facebook before i came across you
    yes i would love to do that
  • William Yates
    William Yates
    Shouldn't that money be given to the government or the UN not kept by 4 generals. It sounds very inappropriate
  • Kelly Anderson
    Kelly Anderson
    yes that is true.. but the money was found and shared in Syria after the mission was over, so i brought mine back to Afghanistan
    now i am looking for a trusted friend which i can send the money to because the money is not safe in Afghanistan here with me
 At this point we were just about to meet friends for dinner.  I only had my mobile on me so couldn't do the background searches I wanted to do but was absolutely sure that this was a scam.  I wanted to wind this guy up.  So I quickly unfriended him on facebook and carried on talking to him.  Thought I would give him a chance to confess about the true nature of his request.

I gave him his chance.  So lets help this man get some money to his son.

  • William Yates
    So how do we get this cash to your son?
  • Kelly Anderson
    Kelly Anderson
    the bank cant accept such cash so i am using a company to send it direct to you.. i am gonna pay all the charges
    all you have to do is receive it
  • William Yates
    William Yates
    What makes you think you can trust me
  • Kelly Anderson
    Kelly Anderson
    i dont really know for now, all i need is your word and i will believe you
    that is why i wrote to you that somebody i can trust
  • William Yates
    William Yates
    Would I get into trouble for doing this? Its just that last time with the Nigerians there was a lot of problems
  • Kelly Anderson
    Kelly Anderson
    no its not going to get you into problems
  • William Yates
    William Yates
    Ok cool
    So what information do you need
  • Kelly Anderson
    Kelly Anderson
    your full name, home address, email, and mobile number
    and a scan copy of your id
  • William Yates
    William Yates
    And my bank details I presume
  • Kelly Anderson
    Kelly Anderson
    that is what the company needs before the money can be sent, they have to know the receiver
    so they will not be any mistakes
  • William Yates
    William Yates
    The company I thought you were sending it direct
  • Kelly Anderson
    Kelly Anderson
    the money will be deliver to you in your home
  • William Yates
    William Yates
    What in cash?
  • Kelly Anderson
    Kelly Anderson
    the company will be sending a diploma down
  • William Yates
    William Yates
    A diploma down. Isn't that an educational certificate
  • Kelly Anderson
    Kelly Anderson
    its a united nation diploma
    and the photocopy of his id will be giving to you also
    that is how things work here in Afghanistan presently
    and the company name is Skynet company, it is all over the world
  • William Yates
    William Yates
    If I doing this for you can you do something for me in return?
    Skynet have you seen the terminator films
  • Kelly Anderson
    Kelly Anderson
    they have assured me there would be no difficulty
    yes i have
    i will be giving you 20 percent from the money
    just let me believe in you

OK he isn't getting my address, ID card, email address or anything.  But I'm not too keen on 20% plus lets throw some other words in there to see if we can throw Kelly off his script:

The address I gave was for the US Embassy in london, the phone number and email are fake.  Also dinner was nearly over so I left and then did some research when I got home.  A google image search for Kelly gave me lots of hits to scam warning websites and lots of other names for 'Kelly'

  • Kelly Anderson
    Kelly Anderson
    fuck of me now
    i am a citizen of US
    you can only report me when my money is in your hands
  • William Yates
    William Yates
    Hi Aaron Ramos
    that picture has been re-used by so many other scammers
    get a new fake picture dude