Skip to main content

I KNEW IT!


I like to think I have a nose for a problem. Not necessarily a bug, but just when something doesn't seem right. The extent to which I follow up on these gut instincts varies depending on how strongly the nagging feeling remains. 

These 'hunches' last for days, weeks or even months, often I struggle to find the vocabulary to express what I am thinking or feeling.

For example, on a past project, the system under test needed to store certain characteristics about a customer (derived from an external service) on their first interaction with the system.

'First interactions' could take a number of different paths. Something about this nagged at me after the system went into live service. I looked superficially several times at the evidence (including with the product stakeholders) and all SEEMED to be well, yet something still chipped away at my consciousness. By now I felt a little crazy, but time and change then proceeded to distract me.

Then the big day came. The information was called from its place of storage to generate a product for those customers to consume. Vast swathes of customers stored data was missing, stemming from a couple of customers flows I didn't anticipate in my testing.

I KNEW IT!

I then talked to the stakeholders involved and reiterated how I knew that something was wrong.

This was a while ago, but I haven't reflected until now. 

I probably have more questions than answers. 

Why didn't I act on my suspicions? Especially if deep down I knew that there was a problem.

Why did the testing originally done against the system not cover these flows? What questions did I not ask of myself, the stakeholders and the system under test?

Why did the stakeholders not buy (further) into my suspicions? Perhaps my procrastination and vagueness didn't inspire them to investigate further.

For now, I think I'll take away as a resolution to act on these hunches with a little more determination and strive the grow the vocabulary and skills required to express myself with greater clarity.

But, one conclusion remains for me, the gut is one of my favourite parts of the testers mindset.

Comments

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…

Getting started with testability

At TestBash Netherlands, I said that, in my experience, a lot of testers don't really get testability. I would feel bad if I didn't follow that up with a starting point for expanding your mindset and explicitly thinking about testability day to day, and making your testing lives better! 

In large scale, high transaction systems testability really is critical, as compared to the vastness and variability of the world, testing done within organisations, before deployment, is limited by comparison. We need ways to see and learn from the systems we test where it matters, in Production.
Being able to observe, control and understand is central to testing effectively, and there are loads of resources and experience reports out there to help. I was/am inspired by James Bach, Seth Eliot, Matt Skelton, Sally Goble, Martin Fowler and a little bit of PerfBytes/Logchat, so lets see if it works for you! 

Overall Model:

Heuristics of Software Testability by James Bach

http://www.satisfice.com/tool…