Skip to main content

Wheel of Testing Part 1 - Motivations



(This will be part of a blog series - part 2 will discuss the content of the wheel itself and what I think it means, part 3 more how it can be used) 

I recently attended the peer conference NWEWT2 in Liverpool, which is my favourite type of conference. You get to share your ideas, have them scrutinised and hopefully walk away a bit wiser. The theme here was "Growing Testers", something that I had wrestled with my whole career, so I looked forward to getting involved. I got some excellent feedback. Also, to my delight, I was also accused of aloof wizardry by Gwen Diagram as I wouldn't offer a definition of 'tool assisted testing' to those who had used the wheel (see above), so I walked away happier and more wizardly than ever.

When I became a manager a few years ago, the world opened up more of the vast variance of human motivation to me. I had to consider contributing the development of others, as well as the self. Problem is I thought I could develop other testers, without really having their buy in, I had the answers. I was completely wrong about that. I had to learn it the hard way. Thats a whole other story but contributes to the existence of this "Wizarding Wheel of Testing".

Hints had been there for a while. Someone said to me while practicing a workshop about "Testable Architecture":
"Why would I need to learn about architecture? I just work on tickets."
Then in a team meeting, someone else said:
"I don't just want to push tickets across the board, but what can I do?"
*Where tickets might be stories, issues, features, enhancements, bugs or whatever on a teams visual radiator/information refrigerator (otherwise known as Jira)

I grant you this is not an overwhelming amount of empirical evidence, but the testers in many organisations I had worked in had such a narrow focus, dictated by delivery demands. How does one open minds but not replace one repressive model with another? Always the danger, replace one tyrant with another? No matter what your original intentions were...

Underlying motivations...

Lets look at what was going on in my mind:
  • Open as many doors as possible - the more doors opened, more chance to walk through them. Literally no one can walk through one for you.
  • Promote questions and not answers - buckets of detail lead to buckets of dependence and dogma. Careful.
  • Not obsessed with definitions - defining things is useful, until it becomes divisive. See 'Testing vs Checking' when used as a stick. Socially generated definitions in organisations through conversation. Useful.
  • Represent the core of a tester - what are the core skills of a tester. Now thats an interesting question. Choose wisely from the multitude. Discuss.
  • Was your career linear? - did your career progress beautifully along a smooth curve? Bullshit. Career models generally ignore the bumpiness of reality. And are created by managers who do not listen to their own experience.
  • More you learn, the less you know - testing is a vast discipline, which is part of its allure. I have no idea how much I don't know. Each segment of the wheel could be a specialism/career in learning in itself.
  • Disciplines overlap as much than they differ - create something that developers. product people recognise too? Similarities as well as differences are important.
  • For the buccaneers - ever seen an organisational career model which reflected never mind rewarded buccaneering learning? They are generally about finishing stuff not learning stuff through broad horizons. 

More here:



Then, the wheel was then born! Gandalf wasn't there. Or Dumbledore. Just me. More soon. 

Original slides from NWEWT2:



Comments

  1. When one door is close then several doors get open for you. You just got to push yourself to look for that open doors instead of looking at close one.

    ReplyDelete
  2. The title itself is motivational. Hope is life so never lose hope and just belive in Allah the creature of everything he surely will help you and will create far better ways for you just have faith and strong belive.

    ReplyDelete

Post a Comment

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…

The Team Test for Testability

You know what I see quite a lot. Really long-winded test maturity models. 

You know what I love to see? Really fast, meaningful ways to build a picture of your teams current state and provoke a conversation about improvement. The excellent test improvement card game by Huib Schoots and Joep Schuurkes is a great example. I also really like 'The Joel Test' by Joel Spolsky, a number of questions you can answer yes or no to to gain insight into their effectiveness as a software development team.

I thought something like this for testability might an interesting experiment, so here goes:

If you ask the team to change their codebase do they react positively?Does each member of the team have access to the system source control?Does the team know which parts of the codebase are subject to the most change?Does the team collaborate regularly with teams that maintain their dependencies?Does the team have regular contact with the users of the system?Can you set your system into a given state…