Manual Testing is dead – long live Manual Testing!

This posting is a little later than planned (by about a week), as I had intended writing it after attending the National Software Testing Conference in London, where I was fortunate to speak as well as attend some great talks. I came away with 4 blog ideas, and this is the first one of them.

The demise of manual testing is being discussed in blogs, magazines, conferences, meetup’s etc. If you look at job ad’s, you’d think that manual testing has already died a death and been buried! They all mention ‘Automation tester’ – like its the ONLY thing that testers need to do. So, it was refreshing to attend sessions where people took a different view of things.

I’ve mentioned before about the need for testers to be able to do manual exploratory testing, and it was great to hear Ingo Philipp from Tricentis discuss this in a conference setting. As an industry we need to push testers back towards performing manual exploratory testing, to be complemented by automated regression testing, otherwise we are going to start missing defects due to deficiencies in the overall coverage.

Think about it. An automated test is only as good as the person who wrote it, and only as up to date as when it was last maintained. An automated test cannot make allowances for something that has changed. It cannot stop part-way through and think ‘I wonder what happens if I click this button rather than following the process flow’. It cannot look at the number of steps and highlight that the application sucks from a usability perspective. It cannot point out that the colour scheme is unreadable, or that the company logo is the wrong colour/shape/size etc. It can only run the steps it has been coded to do and validate against what is has been told to check for. So a test may pass, as the application displays what was expected, but what if additional text is present that shouldn’t be there? The test would pass, and unless anyone manually tested that screen, it would go undetected.

I’m not saying that automated tests are unimportant, far from it, but they have their place within a tester’s toolset and are not the only tool available to a tester. Of course you need to have automated tests in place to be able to follow a Continuous integration process, but automated tests cannot cover every possible scenario.

There is another aspect to this as well. Most applications that we develop are going to be used by human beings, so why do we insist on believing that it is best tested by code, without any human test covereage as well? Automated tests should cover the repetitive tests, the load and performance tests, but a person, a tester, needs to look at the application and think about the different paths that the end user could take.

The fun is in the thinking. The benefits are derived from the thinking. A tester’s brain is needed to assess the tests needed, and I despair when I read of really good manual testers with many years experience who feel that they have to leave the field of testing as they do not have automation experience. I sympathise as I came from a manual background. Coding holds no interest for me – if it did, I would have become a developer. So, my career has been based on testing software and working out how best to do so.

We need to stop this freefall ride into automation oblivion, and look at hiring and supporting multi-skilled testers. If a tester cannot write automated code, does it really matter? Better to have a tester who can look at a requirement and work out what needs testing, than a tester who can code but has no clue how to test something!
Developers can write code, so why not pair a develope with a tester to write the automated tests that a tester defines. If a tester wants to write code, and has the time to do so, then that’s great – but we should not be penalising people for knowing how to assess a requriement and define the tests needed (i.e. the core elements of the job), just because they do not have an additional skill in coding automation tests.

I do feel that there are a number of us trying to push back the tide a little to show people the benefits of doing both manual and automated testing, but the more that speakers such as Ingo and myself are getting out there and promoting the benefits of exploratory testing, the better. We need to stop this damaging trend, and ensure that we retain the best skilled testers before they feel undervalued and move on.

Now, who’s with me on this?

Beating them at their own game!

This is a post about Google Chrome, the F12 Developer tool feature and how I felt very smug after using it to get around restrictions!!

I installed an Ad-blocker into Chrome, which is the main browser I used, and I noticed that certain sites were showing messages asking me to remove the Ad-blocker (like the images below), or sign-up for content – neither of which I want to do to be honest. I have ensured that the sites cannot be identified from the screenshots below, as it is not my intention to draw attention to any specific sites, as there are many out there that have these restrictions in place.


There was one particular article I wanted to read and I could see no reason why I couldnt do so, seeing it as it wasn’t something that was exclusive to this particular site. I could have searched elsewhere, but was feeling in a less than co-operative mood, so decided to have a play.

Pressing the F12 button and opening the Developer Tools gave me the chance to inspect the element on the page that was blocking the text, by clicking on the button (highlighted in yellow)….

….and then clicking on the blurred area on the page that I wanted to inspect:

This then showed the element in more detail and I could then investigate further.

I found that I had two different choices, depending upon the type of restrictions imposed:

  1. To read the plain text within the Developer Tools pane rather than on the screen, but that meant having to expand every element in order to reach each paragraph:
  2. To try removing the blocker itself in order to read the text on screen as intended by just deleting that line of text.

On one site I had to use option 1 to open each element to read it as deleting the element actually deleted the text within. On another site I used option 2, and simply deleted the element off the page and the text was then visible with no restrictions.

I was surprised how easy it was and I guess that over time, the website builders will try to make this more difficult to do, but not many people really know about the F12 function, so I feel it my duty to help spread the word a little.

It really is that simple. If you are not sure, just have a play. If you delete things that you didnt want to, just reload the page and try again. It really is satisfying to beat people at their own game sometimes!



The UKStar legacy


I’m back from the inaugural UKStar event in London, where I was privileged to co-present a talk with   on communication, and it seemed to go down really well. But that’s not the only reason that it was such an enjoyable time.

The venue – County Hall, with a view across Westminster Bridge to Parliament and Big Ben. As a Londoner I have never managed to see the view from there so it was something special. I do have to say that etc.venues did a good job of keeping us fed and watered, and the guys at Eurostar who organised the event were great. They all seemed to really enjoy the event and were super helpful.

The talks – so many great ones and I missed a couple due to clashes that I would love to have been in, but then thats always the case with dual tracks.
I attended the ‘Hey what just Hackened’ half day session with Declan O’Riordan, which helped us look at security testing in a new light, the keynote with Maaret Pyhäjärvi & Llewellyn Falco on the concept of Mob Testing was something new to me. I also enjoyed seeing Paul Collis of the FCA (who I know from the Test Management Forums) do his first conference talk about the transformation of the testing function, Dan Ashby & Hannah Mason speaking about the mentoring and learning opportunities at the Software Testing Clinic ( and also Stephen Janaway’s journey from Test Management to a broader Software Delivery Manager role gave me a lot of food for thought ( The talks were inspiring and I really like the fact that new speakers were encouraged.

The atmosphere – there was a noticable buzz for the whole two days, with so much interaction going on. I think this is one of the best things about any conference – a chance to meet old friends and make new ones, which I did during the Tuesday morning Lean Coffee session, ad-hoc chats over coffee and lunch, and a very nice evening meal after the Monday evening drinks.

So – would I encourage people to attend a conference? Yes! Choose carefully though, as there are many and you want to go to one with a good range of talks so you can maximise the opportunities to learn, contribute to discussions and network.

Would I encourage new speakers to apply? Absolutely! I’m really pleased to see a change in focus at events to actively encourage new speakers, and I will be helping at the BCS to mentor someone this year. I will also speak to Dan Ashby about opportunities to give something back to the testing community.

If you commit to do just one thing this year, then go to a great conference. Be challenged, learn new things and meet new people. What have you got to lose?

2017 – 3 weeks in.

A little belated, but I can get away with posting ‘Happy New Year‘ as this is my first post of 2017.

So, here we are, about 3 weeks in to the year and a lot has happened already:

  • I have taken on a new role in my company as Director of Quality Engineering – essentially Director of the QA function, for a different brand to where I worked before so this has opened up some new and exciting opportunities for me within
  • I recently joined the BCS and am hoping to get involved in their mentoring scheme for new conference speakers – I’d love to give something back to our testing community!
  • An article which I worked on late last year has been published in Test Magazine – and they have done a cracking job of the presentation and layout (thanks 31Media). Its all about where we should focus our efforts as testers when looking at honing our skills, so I would love to hear any feedback if you do happen to read it.
  • I am speaking at Testing Showcase North in Manchester in February on the subject of Tester Training, in a similar vein to the magazine article, but of course delivered as an interactive talk. Details available here
  • Then a week later I am joining my colleague Bhagya Perera in London at the inaugural UKStar event to deliver a session on ‘The Communication Bridge’, which I am very much looking forward to as well. More details here
  • Oh, and in May I will be speaking at the National Software Testing conference in London!

I cant believe how busy it’s been already, and that is without the workshop that I am running with my new team next Friday, and our ongoing QA Chapters that we run in-house.

But I am not complaining, I get bored easily (something that I am not proud of, as I wish I had more patience overall!), so doing a lot of things is good for me. One of my old team asked me last week how I found the time to do so many things. I do wonder myself sometimes, but my reply to her was that it comes down to having an in-built passion to do something of benefit. No-one can be forced to do anything extra – we have to want to. The secret is to find something that excites you, helps you grow as an individual, as well as in terms of job related skills. Giving something back by helping others where you can (it shouldn’t be just about personal gain), and making a difference – these are important to me, and I really hope that 2017 is even more awesome than 2016. Of course that depends on the amount of time and effort I am prepared to invest, so the incentive lies with me – but that’s what is good about it. I am in control and can do as much or as little as I feel capable of doing.

So, watch this space 🙂

Oh, one final thought – my job title is now Director, not Manager, but I think I will leave the site titled as ‘Musings of a Test Manager’, as I still think it sounds good to me. I tried thinking of alternatives, but ‘Doodles of a QA Director’ doesnt really have the same ring!

My first Webinar!

A week ago I delivered my first Webinar, courtesy of Unicom Seminars ( They had approached me to see if I was interested, and after blogging, writing a few magazine articles and speaking at conferences, this was something I had not done before.

The theme was around learning and it worked well for me as I have been on a bit of a mission to help my team to do some tester pairing and Thought Leadership to stretch themselves, and I felt I could deliver something of value to others.

As I was writing the slides (and notes), I noticed just how much we focus as an industry on the purely technical skills that we want testers to have. It struck me that we are ignoring the analytical skills and soft skills that we want as well, which are the three areas I feel a good tester needs to work on. There’s no point in hiring a good technical tester who lacks analytical skills as they wont be able to plan the tests to actually automate. There’s also little point in hiring someone with little or no soft skills. Good communication skills are vital.

I managed to get the point across in a 30 minute slot, with 40 ‘live’ attendees listening in, and I was very pleased to have around 10 questions to answer as well.

Doing something like this has helped me to give something back to the wider testing community in a different way, and I am grateful for that opportunity. My next magazine article will be in Jan 2017 Tester magazine on this very topic so you will be able to read more there. Unicom have also asked me to do a conference session in Manchester in February on this topic, as they felt it would come across well.

I would encourage anyone reading this to have a think about stepping out and giving something back. The Ministry of testing offer the chance to do 99 second talks on a test related subject which can be put on a website, and this is a great first step towards doing a conference talk, webinar or writing a blog or article. It’s worth it, believe me.

Routes into testing

I’m going to make a guess that you (as a reader of this blog entry) never dreamt of becoming a Software Tester when you were at school or college. You may have had dreams of being a doctor, lawyer, train driver, astronaut or a whole host of other things, but Software Tester was not something you would necessarily have even heard of.

For decades, anyone wanting to get into the field of IT would aspire to a Development (or Programmer) role, as these were the main roles that we heard about. Even today, whilst Computer Science graduates have heard of testing, by virtue of the fact that A levels (in the UK) and degree courses now do something akin to a nod towards the fact that software testing is actually something important, and there are people who choose not to write code but to test it for a living. As an example, Oxford university offer a course on Software Testing as part of a Software Engineering degree, which is something that didnt happen in the 1990’s or 2000’s!

There are many graduate schemes which bring people into IT, but even today primarily this is Development, Security and Operations type roles. There are Testing Services companies that will train testers as graduates, but I wonder what the ratio is of graduate testers compared to other roles in IT?

I fell into a testing role for my second job, moving from one bank to another, from a non IT role into a role that I had never heard of. There were no training courses and I learned on the job. It took me a while to understand what the role actually was, and even now there are many people with differing opinions as to what Testing actually is – but that’s not for this post!

Over the past few weeks there have been some interesting Twitter posts about whether Testing is a role that anyone can get into or not. My view is that we are all testers anyway, without realising it. We test the temperature of bath water before bathing our small children. We test the fastest route from A to B and try different ways. We test boundaries of behaviour and acceptability. We test how much we can eat in a ‘eat all you can’ buffet before we feel full. We test just how much longer we can wear our old trainers before they fall to bits! We test all the time.

It seems to me that just about anyone could in theory become a tester, no matter their career background, but not everyone would be good at it. To be a good tester requires having the right attitude as well as technical ability and the right mindset. Technical skills can be learned, how to approach testing can also be learned, but attitude and the right mindset cannot be learned.

It’s interesting therefore to look at how current Testers (at all levels) actually got into software testing as a career. A common story is where projects have required assistance from business units with User Acceptance Testing, and those who helped out became involved that way, staying in Testing and bringing their business knowledge. I’d love to hear your stories as I’m sure there must be some very unusual routes into Testing out there so please share your story and how you found the transition.

Another great day at work!

Ok, I am a few days late, as the day was actually Tuesday 13th September, but I haven’t had time until today to get blogging.

Back in May, I blogged about taking TestBash to work – well we did it again this week! With my colleage Bhagya  we ran our second ‘Building Quality with Distributed teams’ workshop for over 20 people from four different teams within our organisation.

We had learned a lot from the first workshop, namely to have a timekeeper as well as two observers, which really helped, plus we extended the timings of the tasks a little to see how that worked.

We managed to keep it to 3 hours, and with 100% positive feedback from participants that they all found it useful, but almost unanimously suggesting that we add a little more time as it felt rushed as we wrapped up. So, our next one will be 3 1/2 hours long! Each time we will try to take on board feedback and make improvements, so as to maximise the benefits that the participants gain from the time invested – and it looks like we are in demand. Our parent organisation has asked us to perhaps run a session as a pilot to see how that works, and we may we asked to run externally as well.

All of this arose from attending a workshop at a conference, and proactively taking it from there and implementing it ourselves. So thanks again to Lisa Crispin and Abby Bangser  for sharing the resources and supporting us with this. They could so easily have kept it to themselves, but that isn’t what we as testers do. We share our expertise and knowledge with others for the benefit of everyone in the industry, and that’s what I love about the testing community, so long may it continue.

Here’s a challenge. What have you read about, seen at a conference or experienced that you could share with others?