All change!

Well, following the success of my January 1st posting, things on the blog front have been very quiet – but that doesn’t reflect my life in any way at all.

In mid January my role was put at risk of redundancy, meaning a 30 day consultation period that concluded last week. If I am honest, it wasn’t something that totally surprised me, as the tech organisation has been changing over the past 12 months, and the role I had didn’t really fit within the new framework.

So how did I feel? It was very odd, as I didn’t know how I should feel. What should I do? How should I be thinking? Where do I start?
There is no template, and not having been through this before, I used common sense to be honest. I decided to tackle this as a positive thing. My children are 18 & 21, my wife works, so its not as though I am the only breadwinner, and its not the end of the world. I have also worked full time without a break in employment since I left school over 30 years ago, so actually, I felt that I could do with one.

It also struck me that each job change has been to try to move onwards and upwards – and now the cycle has broken. It is really liberating to break out of that process! I had no idea how freeing it would feel.

I work for a great company who have really supported me through the process, putting me in touch with an organisation who support people in their job and career journey after redundancy.

My first task, literally 2 days after I was told, was to set about writing a list of things that I wanted to do:

  • Update my LinkedIn profile
  • Take advantage of the help offered by the company I was referred to for career guidance, and sign up for sessions/webinars etc
  • Update my CV
  • Speak to contacts
  • Order business cards to give out at conferences/meetups etc
  • Look into contracting (I have only ever been a permie)
  • Sort out my shed
  • Clean the greenhouse
  • Fix the shower grouting
  • Plan my radio shows in advance

And so on. It was a random mix of things that I wanted to do, including jobs I had put off and not done, so the idea was to keep busy.

I kept a list of what I did each day – job alerts, agency contacts, applications, webinars attended, shed tidying etc so I could see the journey, and it helped. Being productive and organised is important to me, and I made sure to get up around 7.30 each day so as not to get into the habit of sleeping in late!

So – why update now? Well – things don’t always go as planned. In my mind, I was all set to leave on the 14th Feb, I was fine with that, and had made plans for the 15th & 16th so I would not stop work and suddenly feel a bit adrift. And then the week before, I had a conversation which changed things.

I was asked to stay on until the end of June as an Interim Project Manager in the team I was with up until January 2017, as my domain knowledge would be beneficial. I said yes, and start on Monday 19th. I am looking forward to this – not only does it buy me some more time, but with stakeholder management, delivery and workshops a part of the role, these are things that will help boost my skills. It’s not strictly a Testing role, but there is a lot of crossover, as an increasing number of Test Manager/Head of Test roles are looking for these things, and I have the chance to be doing them now. It’s a win-win.

I feel very fortunate to have been asked, and glad that I approached the whole redundancy process with a positive mindset. Although the redundancy is deferred, I can pick up the search again in a month or two when I am ready, so nothing I have done or learned is wasted. If I hadn’t been through the process, my CV would not have received it’s overhaul, so at the very least, that’s been worthwhile!

Every experience is an opportunity to learn, and we all have the choice as to how we deal with whatever life throws at us. I can empathise first-hand with others who have gone through the same process rather than offering platitudes, with no idea of how that person may have felt.

It’ll be interesting to post again in 6 months and see where life has taken me. Who knows!

Advertisements

My hope for Testing in 2018…

It’s the 1st of January 2018, and at 3pm the rain and grey skies have cleared, and a little blue sky and a few rays of sunshine appear. It’s that little ray of hope in an otherwise grey day that helps make me think of the future, and to wonder where we as an industry will be at the end of the year.

What will be have learned? What will we be doing differently? What new skills and approaches will we have adopted? How will our jobs have evolved?

I have one overriding hope for the testing industry this year, and that is to finally put aside the obsession with just one aspect of the testing craft – ‘Automation’.

There have been so many debates and I think to be honest it’s time to move on, as it is an unnecessary distraction from other things that we should be discussing.

I am going to quote James Bach here (see Testing vs Checking), and the White Paper that you can link to from that page:
“The trouble with “test automation” starts with the words themselves. Testing is a part of the creative and critical work that happens in the design studio, but “automation” encourages people to think of mechanizable assembly-line work done on the factory floor.”

Testing is a craft. It is something that requires thought. It requires a skill to be able to identify what needs to be tested and how to go about testing.

Automation is just the ‘how’, which is fine, but with the focus very much on the ‘how’, we seem to have overlooked the importance of the ‘what’. 

Various comments on LinkedIn by other testing professionals have suggested that this demeans the craft – and I have to agree. Anyone who is not a tester/has no testing background, maybe in a senior management position with budgetary control, may well look at the testing activities, and assume it’s basically writing code to perform tests. This does not help us to showcase the thought processes that we have to go through to identify what needs to be tested – using risk based approaches, exploratory testing, story walk-through’s and our own experiences in general to work out how to try to break something that hasn’t yet been built.

Test automation looks great on paper – who doesn’t want to save time, and get rid of the boring repetitive work. It’s an easy sell. And in theory if we can automate a bunch of repeatable tests, then we have time to spend elsewhere. However this is not always the case. Because we only ever discuss automated tests, senior management can lack visibility of the other types of tests that need to be factored in, not to mention that if you leave an automation pack untouched for any length of time, it will need some work to get it running as there are bound to have been changes to the application in the mean-time.

Lets assume we are testing a new web page. The testers do some manual tests and then start to write automated tests to cover the scenarios. Unless they know otherwise, a team can then assume that the job is done – we have repeatable tests so lets move on. But the automation that is so often talked about covers just ONE PART of the testing needed – Regression.

So – what about performance and load testing for example? Where do they fit in? Another tool is needed to create load tests, but there is also the critical thinking needed to establish what the acceptable performance benchmarks are for 1 user, 10 , 100, 1000 etc. And then the understanding needed as to how to scale up the load tests – do they all repeat the same scenarios, or do we try to mimic user behaviour? The running is the last element of a long thought-driven process.

And I haven’t really covered the benefits of exploratory testing. I’ve raised this point in a previous post – automated tests cannot stop part way through and do something different. Not yet anyway – maybe that’s something that machine learning will introduce! But for now, automated tests will just keep doing the same thing over and over again – checking.

This is not testing.

I’ll repeat myself here – testing is the thinking, the investigating, the risk assessment, the planning of what we need to do, looking for things that have been missed by whoever created the requirement – something that they had never considered could happen. After that, it becomes the ‘how’ – what is the best way to perform the tests – as a person using a keyboard to navigate our way round a web application or by writing automated tests to do that for us in a repeatable way.

My wish for 2018 is that we stop making it seem as though testing is all about the automation. It is not. We are far more than writers of testing code, so let’s showcase what we do that adds real value to our organisations.

We are the critical thinkers – let’s be proud of that.

Happy New Year!

 

My reflection on 2016

This will be my last post for 2016 so I thought it an idea to reflect back on what has happened this year.

2016 has been a great year work wise (and personally too, but this is more of a ‘work’ type blog, so I’ll skip that). I’ve continued co-running our RBI global QA Chapter with Bhagya (https://bhagyagdm.wordpress.com/), bringing 75 testers together on a quarterly basis to create a testing community, where we help each other, ask questions, give support, perform demo’s etc, and we are looking at how we can reboot the Chapters for other disciplines.

I’ve also been jointly running the Distributed Teams workshops with Bhagya which we both learned about at the March 2016 Test Bash from Lisa Crispin and Abby Bangser – we have done 3 internally, and all were very successful.

In April at the UK Test Management Forum, I presented a talk on the Challenges for Test Managers, as there are less of us. What does the future hold? It was an interesting discussion and led onto another talk in December – see below!

From TestBash, I brought back to my team the concept of Lean Coffee meetings, and we adopted those for our team meetings and also for the QA Chapters – hugely successful as it gives every tester a voice, whether they are shy and unused to speaking openly or not.

Then I found that I spent the summer preparing for a busy Q4:

In October I presented by first Webinar, thanks to Unicom, on Being a Better Tester. It went down so well, that I am now presenting it as a talk at Testing Showcase North in Manchester in February 2017!

In November I had an amazing visit to India, where I was privileged to speak in front of a large number of testers about Being a Better Tester – essentially delivering my webinar live. Also I ran a smaller version of the Distributed Teams workshop for the team we work with and they found it hugely informative. (More details on my India visit blog page).

And in December, I spoke at the British Computer Society, Testing Interest Group on ‘Challenges for Test Managers’ after being invited to do so, following on from my April session. It was a privilege to be asked and to be able to run an interactive session with a larger number of attendees, which I felt was very rewarding. I have just typed up a small article for the BCS Tester magazine to report back on the talk and the ideas that came from the audience, as I find that a lot of conferences don’t do enough of this – we should do more interactive thought gathering sessions and share that around.

It feels that this year has been about adding value to others. Giving something back and helping others to do their jobs better – this is the reason I go to work, and why I do conferences, articles and this blog. If I am not making a difference, then what is my purpose? It’s something that is very important to me.

So, now I am starting to look forward to 2017, and there’s a lot lined up already:

  • I have a magazine article coming out in January (Test Magazine) on ‘Changing our approach to Training – how tester training needs to evolve’.
  • In February I have the Manchester talk.
  • A week later Bhagya and I are leading a session on Communication at the inaugural UKSTAR event, which I am hugely excited about.
  • In May I am hopefully speaking at the National Software Testing Conference.
  • I have also volunteered to be a mentor to a new speaker, which will happen later in the year.
  • And I am still involved in helping with the UKTMF, which will be getting a revamp in 2017.

It’s great to have all this planned before getting to the end of 2016, but it takes effort. Nothing just falls into your lap – I have had to put myself forward to do these things, and it is definitely worth it.

If you have read any of my postings this year, I would like to say thank you. I do enjoy receiving comments – I know that someone has either found it useful or challenged enough by what I say to respond. Without readers, it wouldn’t be worth doing!

I wish you a very Happy Christmas and a prosperous and successful New Year. Here’s to 2017!