Skip to main content

Your tests tell the real story.......

Projects and products are increasing in complexity. That’s life at the moment, ask our many financial institutions. Change embracing methodologies, legacy systems interfacing with new development mean that most systems of documentation struggle to keep up, coupled with the belief that being ‘agile’ means that even basic documentation is frowned on.

We, as testing focussed individuals are perfectly placed to bridge that gap. An organic set of acceptance, exploratory and automated tests which flex with changing business needs and technical design modifications, document the flow of the project and patterns emerge for key decision points. Coverage areas, non-coverage areas, tests which prove legacy behaviour, new tests added, and old tests retired as functionality has changed all add context to the project or product story.

This is also a slight riposte to the ‘automate everything’ theory, clicking ‘go’ is not a facilitator for analysis or learning. Learning is gained from a stepped approach, I have fielded arguments that it’s a little heavy, but I think in terms of story telling a little effort goes a long way.
  • Mind Map – for each item of work (user story for example), create a mind map, nice and simple. This is your one stop shop for recording business needs, test ideas, caveats, technical details and anything else you wish to record. This tells the project story at a high level without too much detail and acts as a prompt for conversation. Print off and make it visible every so often.
  • Test Management Tool – this usually raises a few eyebrows, given the current mood in a lot of organisations. I see tests being created all over the place in text files, spreadsheets and a plethora of other tools. If your organisation has a Test Management Tool, don’t fight it and use it to store acceptance tests. You get free version control and safer storage in the main. Creating your business driven, scenario based tests and storing means you have one place to begin collaborating from.
  • Automation – You might have many automated tools, for creating data, setting environments to the right state and tests themselves. Regardless of tool choices, your tests should tell the story from a business facing point of view. Better to say ‘Create an Online Customer with a Balance of £50’ rather than the ‘Insert Cust into Offshore DB’. And comment your code; the amount of non commented test automation code I see is frightening.
 So, tell the story of your project or product and use the above thoughts to radiate that information. The team will thank you for it as future decision making is much better when history and context are simple to find.


Popular posts from this blog

A Lone Tester at a DevOps Conference

I recently had the chance to go to Velocity Conf in Amsterdam, which one might describe as a DevOps conference. I love going to conferences of all types, restricting the self to discipline specific events is counter intuitive to me, as each discipline involved in building and supporting something isn't isolated. Even if some organisations try and keep it that way, reality barges its way in. Gotta speak to each other some day.

So, I was in an awesome city, anticipating an enlightening few days. Velocity is big. I sometimes forget how big business some conferences are, most testing events I attend are usually in the hundreds of attendees. With big conferences comes the trappings of big business. For my part, I swapped product and testability ideas with Datadog, Pager Duty and others for swag. My going rate for consultancy appears to be tshirts, stickers and hats.

So, lets get to it:

3 Takeaways

Inclusiveness - there was a huge focus on effective teams, organisational dynamics and splitt…

Wheel of Testing Part 2 - Content

Thank you Reddit, while attempting to find pictures of the earths core, you surpass yourself.
Turns out Steve Buscemi is the centre of the world.

Anyway. Lets start with something I hold to be true. My testing career is mine to shape, it has many influences but only one driver. No one will do it for me. Organisations that offer a career (or even a vocation) are offering something that is not theirs to give. Too much of their own needs get in the way, plus morphing into a badass question-asker, assumption-challenger, claim-demolisher and illusion-breaker is a bit terrifying for most organisations. Therefore, I hope the wheel is a tool for possibilities not definitive answers, otherwise it would just be another tool trying to provide a path which is yours to define.

In part one, I discussed why I had thought about the wheel of testing in terms of my own motivations for creating it, plus applying the reasoning of a career in testing to it. As in, coming up with a sensible reflection of real…

What if information isn't enough?

One of my aims for this year has been to attend/talk at what I will class for the purposes of this blog as 'non-testing' events, primarily to speak about what on earth testing is and how we can lampoon the myths and legends around it. It gets some really interesting reactions from professionals within other disciplines.

And usually those reactions (much like this particular blog), leave me with more questions than answers!


After speaking at a recent event, I was asked an interesting question by an attendee. This guy was great, he reinvented himself every few years into a new part of technology, his current focus, machine learning. His previous life, 'Big Data', more on that later. Anyway, he said (something like):

'I enjoyed your talk but I think testing as an information provider doesn't go far enough. If they aren't actionable insights, then what's the point?'
This is why I like 'non-testing' events, someone challenging a tenet than has be…