This poem was performed at Test.Bash() Manchester in their 99-second talks. This was inspired by Krissie Barrick’s talk at Accessibility Nottingham about a day in the life of a person with disabilities
A testing poem performed at TestBash Manchester 2019 and inspired by Tony Walsh’s Take This Pen
I’ve been a member of the online testing community for a long time, initially though Twitter by following some testing ‘names’ and then through the Ministry of Testing. A lot has been written about how welcoming the Ministry is and how they put inclusion and diversity at the forefront of their thinking and planning and I can only echo that. They have not only helped me improve as a tester, they have helped me improve as a person and had a massive and unexpected impact on me. They helped me be braver!
I’ve written poetry and parody lyrics to songs since I was young. These were always for me, with a couple of minor exceptions to my partner! You know, valentines and other mushy stuff… But something happened along the way and posting my first foray into testing related output (https://www.thebigtesttheory.com/blog/2017/11/26/if-ady-stokes-2017) in the club as well as my blog (which was also for me, never expected anyone else to read it) was a very big step for me. It took a long time for me to decide to share, then even longer to hit the Create Topic button. Fortunately there are some very kind people in our community who enjoyed it and encouraged me to do more.
At Brighton in my talk, Test all the Things with the Periodic Table of Testing, I had an irrational idea to create a song for people to join in and hopefully remember my table. I always get nervous before talking but it was several levels raised above normal thinking about singing (well, what I call singing) in public. Again I was encouraged by many but I need to shout out to Gem Hill and Emma Keaveny (our brilliant Essentials host) for their encouragement. To quote Emma;
Yes my friend, be brave! It’s the best place to be brave.
And it was! Despite my shaky voice, messing up the last chorus and going out of rhythm I did it! With more help from the amazing Gwen Diagram and João Proença through a Twitter request I had my support and the whole crown joined in. Warning, if you play this, you will hear my truly awful singing. No excuses, but it is a bit out of sync… honest… 😊
Lyrics below if you want to see but the story isn’t quite finished…
Two days later I was even braver in the 99 second talks at TestBash. I read out my poem, Does it Work. The very first time I have ever read out one of my poems. I was shaking badly throughout to the point I nearly dropped the mic (not in a cool at the end way like Vern Richards (love him) suggested).
Being brave can sometimes have its rewards and mine was incredible. I’ve been a long-time admirer of Angie Jones and was fortunate to sit on the same table of her for TestBash. It literally made my week when I collapsed in my chair, stunned by the reaction and that I had actually beaten my fears, and Angie high fived me and said, ‘good job’. I have had it confirmed that despite being a 52 year old the correct label for my reaction was that I had a complete ‘fanboy moment’! I make no apologies for this, Angie is a legend, period.
If you take anything away from my ramblings please let it be, be brave. I am very confident in saying that whatever it is, whatever you want to try, we got you. Me, Ministry of Testing, the whole community. No judgement, just love. Be brave.
We Will Test You (music by Queen; lyrics by Ady Stokes)
Buddy you’re a visual heuristic
Describing the breath of the testing universe
You got elements in place
Paths you can trace
It’s something you can use all over the place, Singin’
We will we will test you (come on)
We will we will test you
Buddy you have different elements
Covering how you can test all the things
You now have a place
You can embrace
You can use this table all over the place
We will we will test you (with the periodic table!)
We will we will test you
Buddy you can scope your projects
Listing all the things that you want to test some day
No mud on your face
It’s no disgrace
To help you test the things give it pride of place
We will we will test you
We will we will test you
‘If’ by Rudyard Kipling was written in 1895. Here’s my version, if Rudyard were a tester. Please excuse the artistic licence!
If – Ady Stokes 2017
If you can keep your head and explain the quality of the product that’s due,
When all about you are losing theirs, and blaming it on you.
If you can trust yourself when others are doubting you,
But make allowance for their doubting too.
If you are treated worse than you really should,
Or there’s misunderstanding of what you said,
And that the future doesn’t look too good,
Or being told that your art is dead.
If you can advocate your worth and believe in testing’s value,
And think of every possible practical scenario that could transpire.
If you can dream of all the things the customer might do,
Then analyse the results to take your testing higher.
If you can meet with Triumph and Disaster,
And treat those two impostors just the same.
If you can script, but not make scripts your master,
And make discovery of truth your aim.
If you can force your heart and nerve and sinew,
To serve your turn long after they are gone.
And so hold on when there is nothing in you,
Except the Will which says to the team: 'Hold on!'
And explain simply your deductive and inductive reasoning,
That was led by curiosity and guided by your intuition.
If you can hear bias arguments but smile and keep on listening,
Then use soft skills and diplomacy to keep everyone on mission.
If you can talk with crowds and keep your virtue,
Or walk with Management - not losing the common touch.
If neither foes nor loving friends can hurt you,
If all stakeholders count with you, but none too much.
If you can fill the unforgiving minute, (or 99 seconds)
With sixty seconds' worth of testing value.
And find a great community who’s in it,
To share their knowledge and is truly diverse too.
If you can treat everyone equally,
No matter their difference to you.
If you can treat their gender, origins and history,
As valuable to offer a different view.
If you can be an ally to all those who need,
And defend their right to be just who they are.
Support everybody’s rights to succeed,
And mentor their journey so they may go far.
If you can see scenarios that will make the testing great,
As well as the risks that others do not spot.
If you can see the value in which tests to automate,
And more, the value in which to not.
If you can use tools to add value to your quest,
But understand their value to aid and not replace.
If you’re not afraid of change and always do your best,
And can interrogate a database.
If you can be the personas and advocate for all,
And the voice of the customer in use and value too.
And advocate and test for your product to be accessible to all.
Explore to make discoveries because that’s what you do.
If you accept that those discoveries,
Will change what you thought you knew.
Look for threats and system recoveries,
And help defend against those too.
And then know all these things here,
Are just a part of what you do.
And be brave and show no fear,
Accepting our learning will never be through.
If your passion for testing means that you will never quit,
You will be here to the end.
Yours is the Earth and everything that's in it,
And - which is more - you'll be a tester, my friend!
SB – Session Based Testing -
Sub section – Approaches
Since Jonathan and James Back (satisfice.com/sbtm) documented their Session Based Test Management approach combining exploratory testing, risk management and ‘management’ oversight there has been a lot written. Hopefully by now most people know the benefits of exploratory testing and some of the various methods of recording that activity. In this article I hope to share a brief overview so we are on the same page. A list of the main benefits and some minor drawbacks. And finally the question technique I apply when using this in my day to day work.
The Session Based Testing approach was developed for a project to allow their test team to ‘organise their work without obstructing the flexibility and serendipity that makes exploratory testing useful’. They needed a way to keep track of what was happening, so they could in turn report back to a ‘demanding client’, while ensuring the time spent created the biggest return on investment.
Essentially this is structured
to help organise thoughts, capture questions and insights and allow rapid feedback. Key elements to this approach include;
- Each session is chartered (associated with a specific mission)
- Uninterrupted (as much as is possible)
- A template is used to record the details of the mission and findings
- Reviewable ( a ‘report’ is produced to document findings and questions and the tester is ‘debriefed’)
- Time-boxed (with flexibility but generally no more than 2 hours)
In my opinion, there are a number of flexible points in the approach and tips that are worth being aware of, especially if you’re doing this for the first time;
- I don’t think it matters if you call it a charter, mission or focus. As long as you generally stick to your subject, although picking one might help when sharing for consistency.
- Interruptions should be avoided if possible. On occasion I’ve shut down Outlook and put my headphones on for these types of sessions. At one time I even had a red flag on my desk which indicated do not disturb unless it was urgent.
- There are templates available or you can create your own like I did. Again it’s useful for consistency to stick with one you’re happy with.
- Reviewable. A lot of focus is on ‘management’ reviews but team, peer or even self is fine, as long as what you find generates actionable insights rather than getting filed away never to add value.
- Time-boxed. If you start small with something very specific that’s a good way to get a feel for this technique and learn to focus. I can sometimes be like the dogs in ‘Up’ and be distracted by squirrels! Learn to note where the squirrels are and why you need to look at them later.
Question technique and template:
I admit that I often use this as a mental reminder, rather than something to populate, as my preference is to speak to a developer on my team immediately after a session to investigate or question. (I don’t raise bugs I describe behaviour and in writing this, that’s probably what my next post will be on. I’ll add a link to it on here when done.) Only if this isn’t possible due to availability will I actually fill things in from the notes I have taken during sessions. For me, this is a disposable document with a short shelf life used to capture, discuss, resolve (or not), and most importantly discard.
I’ve reproduced the template in bullet form rather than embed a PDF or word document, that way I hope it will be easier for you guys to take away and make your own. When you get to the questions you might find, as I do quite often, you will remove some before you start as not applicable, or you won’t have filled some in when you’ve finished. It’s supposed to be flexible like that but you should take a moment to understand why they are not populated or applicable to the session as that may prompt some other thoughts.
- The Basics: Date; App/function under test (brief description); any other useful information depending on your context
- Any dependencies vital to the testing (connections, files, data, hardware etc. this helps make sure you have them before you start)
- Any information that is useful such as material/learning’s from previous sessions, personas to use, environments, tools etc.
- Test strategy (a consideration of techniques you might use as a flexible plan is often more useful than no plan, but don’t be afraid to improvise as that’s half the fun and discovery may make your plan obsolete quite quickly)
- *Metrics (see rant at the end of this post)
- The questions: (with a brief reasoning for them)
What do I expect? (even if it is something brand new I always have some expectations)
What do I assume? (sets a context that I can query as I go)
Are there any risks I should be aware of? (to execution, the system, helps anyone else reading have context)
What do I notice? (behaviour; usability)
What do I suspect? (things that I feel, not always based on facts but that I don’t want to lose)
What am I puzzled by? (behaviour that doesn’t feel right)
What am I afraid of? (high priority concerns about the item under test)
What do I appreciate/like? (always good to have some positive feedback)
Debrief (originally between the tester and a manager there’s a checklist of questions on
. My version is more often a conversation with the developer with questions or queries, but can also be with the product owner or stakeholder depending on what I find/context. I’m not saying don’t do this, rather do it only where it’s going to add value.
This post is getting a bit longer than I’d hoped but I feel it’s important to summarise the benefits and possible drawbacks of using this method so there’s a balanced view.
Allows control to be added to an ‘uncontrolled process’
Can be harder to replicate findings as full details are not captured
Makes exploratory testing auditable
As a ‘new’ technique it has to be learnt
Testing can start almost immediately
Recording exploratory testing (rather than brief notes) can break focus / concentration if you're more worried about doing it
Makes exploratory testing measurable through metrics gathered
Time is required to analyse and report on metrics
Flexible process that can be tailored to multiple situations
Time is required to discuss/give feedback to potentially the ‘wrong’ person
Biggest and most important issues often found first
Can help explain what testers do to clients, stakeholders and the uninformed
Given all the above, if you have to justify exploratory testing, (notwithstanding you should be looking for a new job!) then using session based test management either in its original form or some hybrid version could be the convincer you’re looking for. In the table above, ‘management’ will generally only see the Pro’s column which covers a lot of the things ‘they’ will worry about. But seriously, look for a new job!
*Metrics: I personally don’t think these are useful for virtually anything (oh, more controversy!), but if you absolutely have to report back to someone, a manager who knows little or nothing about what testing really is for example, here are some metric examples. How much time you’ve spent such as start/end times on actually executing testing; blocked; recording findings; actionable insights; questions/queries; potential problem; bugs; obstacles; screen shots or some other method of recording or documents to show any issues to help replicate them.
- As a Tester, how do you grow to keep up with the current trends in testing and development?
- As someone responsible for leading Testers, how do you help Testers grow?