James Whittaker

I met James Whittaker last night at a EuroSTAR event. 

He did a presntation called "10 Minute Test Plans" and it waas great. 

Main points:

• Tradition test plans are not fun to write and not fun to read.
• Worry about 80% of stuff to test and the the other 20% will get covered eventually by doing such things as Exploratory Testing
• Include what is important: the attributes, components and capabilities
• Carry out attribute component capability analysis
• Use an only planning tool (Testify) which also assists in a risk analysis to be carried out
• User Stories and Exploratory tests can be created based on attributes in the plan
• Establish a sub-set of attributes
• Create some pictures showing TRENDS; using metrics can be dangerous
• Everyone in software development/test can get pleasure from looking at the trend graphs

After the presentation I met him for a drink along with everyone else that was at the meeting.  He was really nice to talk to and his views on testing are refreshing.

I am very happy!

Michael Bolton's Rapid Software Testing Course

Michael Bolton taught me, and others, Rapid Software Testing during the beginning of April 2011. It was three days of being presented with a huge range of thought provoking ideas about how to do testing better. Students were frequently given exercises to make them improve thinking and solve problems.

Testing goes further than seeing if a product works as it is expected or assumed to work. Questions come to mind are: What is a Tester and do they assure quality? What is the difference between a bug and an issue? When do you stop testing? What is the coverage of testing that has to be carried out? What is the significance of a Map? How much documentation do you need before testing starts? How can you start testing without knowing how the product is supposed to work? What is a test oracle? What is a heuristic and how do you use them in testing? What is the difference between a heuristic and an oracle? How do you use mnemonics? What is Exploratory testing and what is Session Based Test Management? Which strategy / test approach to doing software testing is best for me? Do I have all the information I need to start testing? What questions should I ask before testing and what if I don't get the answers I need? How do you keep testers interested in doing testing? What skills do I need to be a good tester? Do I need to have ISEB/ISTQB certification in Software Testing? What other resources are their available for me to learn more about testing? What testing books should I read? What are the common problems faced during testing and how can these be overcome? Should I be concerned about doing Agile testing? What is the Context-Driven School of Testing?

Testing is not simply about finding out if a product works. It's better for test teams to focus on how products work if we supply them with diverse test data beyond the sorts of data we assume it is supposed to handle. Try to find ways of producing a variety of test data in the quickest way possible. Look for common patterns and discover test data that does not fit a pattern. Use your mind more often and discover new tests during test execution instead of trying to come up with most of the tests before-hand. Don't put all your trust into requirements specifications and design documents and realize that testers are looking more for the unknown unknowns and trying to make all the risky unknowns known.

Michael supplied us with lots of slides, documents, example test applications for us to look through at our leisure. He gave us copies of slides that he skipped over quickly or never talked about during the three days of the course. There is just so much information available and the course just gave us information to use as a foundation of our learning. The learning is not meant to stop when the last day of the course is over. In fact Michael was also learning from his students, since people with new eyes also have new ideas and new ways of looking at things. Frequently you would see Michael right something down that a student said that he never though about before.

Something that I was really surprised about is how few people wanted to go for a drink or food at the end of each day. A course like this is not just about learning from the person standing at the front but also learning from each other and sharing thoughts about the course. Students were invited to go out in the evening but unfortunately most wanted to get back home as soon as each day ended. This was a disappointment for me since I like to network with other like minded people and find out how they do testing compared with me.

At the end of day one Michael, I and another student went to the London Tester Gathering to meet other testers who work in and around London. Michael gave an interesting talk about test estimation and then I chatted to people for the rest of the evening. At the end of day two I went for a meal with Michael and another tester, where Michael got us thinking again about testing and talked a lot more about his experiences.

Overall I thoroughly enjoyed the three day course and Michael is a wonderful tutor. I highly recommend it to all testers, new or experienced.

Silly questions get silly answers or none at all!

Some people ask questions without searching for the answer first. Check out: "How To Ask Questions The Smart Way": http://tiny.ly/kWjF

Favourite Pubs: The Mud Lark

If you fancy a pint before heading off home via London Bridge railway station then I highly recommend the Mud Lark.  The ale is always in good condition and a joy to drink, the food also looks great although I've never tried it.  Make sure you ask to top your glass up to a pint because I have frequently been served slightly less than what I've paid for!  Other than that it's a very sociable place with music to keep you awake and beer flowing all evening.

http://www.nicholsonspubs.co.uk/themudlarklondonbridge/

A tester who doesn't think is not a tester

I attended a seminar by Janet Gregory recently, titled "In The Brain of Janet Gregory: About Learning - for Agile Testers", provided by Skills Matter http://bit.ly/hl7wiR.  One topic (the main topic) was titled 'What skills do we need?' and covered six main areas: Thinking Skills, Soft Skills, Agile Principles, Technical Skills, Specific Testing Skills, Domain Knowledge.

I was able to see the entire presentation and really enjoyed it (considering that I raced across half of London, arrived slightly puffed out, dying of thirst, but was actually only 2 minutes later than the scheduled start time).

Janet has a wonderful way of presenting: clear, at a steady pace, with slides that don't bombard you with information all at once, and narrative that complements and explains the contents of slides to help you understand.  I've seen so many presentations that just overload or don't really get the main points across very well.  This is an example of a really good presentation.

Now to the point: "A tester who doesn't think is not a tester."  This was a point James Bach made in his blog http://bit.ly/bTlJDJ.  Now I think this is a bit of an obvious statement but in my early days of testing I frequently desired putting thinking aside to follow everything stated in a test script.  Testers can get hung up on the detail of a manual test script and forget the main purpose of trying to discover defects.  It's not, in my opinion, necessary to produce a master piece of a document which leads to a tester mindlessly trying to ensure that an application does what it's expected.  "Executing a test script is simply not enough!" A tester has to think.

All testers need Thinking skills!

Thinking skills include: Problem Solving, Systems Thinking, Innovation and Observation.  Janet Gregory explains this very well in the Skills Matter podcast: "In The Brain of Janet Gregory: About Learning – for Agile Testers".

Welcome

Welcome to my blog all about software testing.  If you don't need information on testing and software then you are looking at the wrong blog.  If you love testing and want to find out what I think then you have come to the right place.

Please feel free to comment on anything you read here.  I'd love to hear from you.