Skip to main content

Testers: Be more like a Super-Villain!

Who doesn't love a Super Hero? Talk to my son, and he'll tell you how much he loves them, talk to many adults and they'll say the same! Deep down, we all love to be the Super Hero, we all want to save the day! However, I want to talk about the flip side of Super Heroes, the Super Villains...

I often play Imaginext with my son, and I (unfortunately?) am nearly always the Super Villain! Be it Lex Luthor, Joker, Two Face, Mr Freeze or The Riddler! These are all great characters and great Super Villains, but why would I want to write about Super Villains?

A while ago where I worked, we had a few Super Heroes, people who would be able to come in and "fix" things that had broken and help deliver projects on time. We then shifted, we decided to do away with the Super Hero culture and try and prevent from being in that position in the first place, whilst we didn't go as far as wanting to hire Super Villains, it's definitely a story that has stuck with me and these two things combined are probably to blame for this blog post!

Let's have a look at some common traits of Super Villains (please bear in mind I am generalising somewhat!):

Super Villains can generally be:

- Experts at what they do - They know what they are doing and how to do it, they are often technically gifted with a great super mind. Mr Freeze was an accomplished cryogenicist!
- Intelligent - Sure, Iron Man and Batman may be brainy fellows, but there's a reason why supervillains are the ones who earn the appellation "mastermind." The Leader, Brainiac, Dr. Doom,  are all extremely intelligent Super Villains.
- Persuasive - They persuade people to follow them, they make people believe in what they want to achieve and in doing so end up with a small team of followers who listen to their every word. Loki, Emma Frost, Mad Hatter are all expert at mind control and persuading!
- Charismatic - Related to the above, but they are very very charismatic, which helps inspire their team of crooks and villains to work together. The Joker is a very charismatic Super Villain, I mean sure he's crazy! But that's part of his charm!
- Passionate - They love what they do, they speak passionately about what they believe in.

Very much a generalised view of Super Villains, but I'm sticking to that for the sake of this blog post!

Now lets take a look at some of the traits of Super Heroes (again, generalising but you get my point):

- Reactionary - They are great at reacting to things, to try and avert disaster but really they're not very proactive in stopping things happening in the first place!
- Super Serious - Most super heroes aren't the type of people who are charismatic and can get people to listen to them, in fact they are often misinterpreted! Superman and Batman are both extremely serious people who can't necessarily take a joke or laugh at themselves!
- Boring (?) - Super Heroes are very very predictable and not the type of person you'd want to have a lengthy discussion with about anything!
- Lacking Communication Skills - Often the super heroes aren't great communicators and struggle to get their points across

What do Villains actually want?

Most Villains want to change things, they want to challenge the status-quo. Another problem with Super Villains is the way they go about implementing their change, and this is obviously one trait that isn't good!

Lets take a look at some Super Villains who wanted to inspire change:

- Syndrome from The Incredibles: He is a perfect example, he wanted to democratize super powers so that everybody could be a super hero, not just those who were born to the right families could be super. (Obviously how he went about this is not the best idea)

- Dr Doom - He has accomplished world domination a few times, and he even changed the world for the better!

- Lex Luthor - He wanted to use alternative energy when he was president, that's not a bad idea is it!? The only problem is that him and Superman just don't get along!

- Poison Ivy - She wanted the world to have more plants! Not much of a Super Villain if you ask me!

So how does this all apply to Testing?

So, looking at the views of both the Super Villain and the Super Hero above, who would you say is the better person to aspire to be? Especially as a Tester...

If we were to take the above in to consideration alone, then in my eyes I would have to say (somewhat unsurprisingly given the title of this blog post!) Super Villain... In fact if a Tester were to come to me with the traits of a Super Villain that I listed above, I would be very excited to interview them and potentially hire them!

To me, testers (in fact any professional in any discipline) should be people who want to inspire people, who want to talk and communicate with all forms of people in the business, they should be experts at what they do, and how they do things.

Again these are all things that I would value highly in a tester, but as well a tester should be questioning things and wanting to improve things for the team. Perhaps this is where the lines become blurry, most Super Villains want change predominantly for personal reasons, whereas we should want change to improve the team, and in turn improve the quality of the product that we are testing.

So Testers who are reading this... be more like a super villain! (Unless you want to take over the world and kill everyone... in that case please don't!)


  1. The relationship of DEV and QA shouldn't be one of an artist and an art critic.

    It should be more like the one between a writer and a copyeditor, working together to make a quality product.

    -T.J. Maher

  2. This concept is on the rise more in the animations and sci-fi films where the villain has some extra powers and the whole story or more particularly the climax is based on the fight with that super villain.


Post a Comment

Popular posts from this blog

Advantages of using Test Management tools

Before I start talking about test management tools, let me clarify what I mean by the term test Management tools...  I am not taking about your office excel program where you store your test cases in. I'm talking about bespoke test Management tools, your quality centers or Microsoft test manager...
In the strict case of the term test Management tool, Microsoft Excel can be used as such, but heck, so could a notepad if used in the right way... For the sake of this blog post I am talking about bespoke test Management tools.
Firstly, what test tools are out there? There are many more out there today than when I first started in QA over 5 years ago. When I started the market was primarily dominated by a tool called Quality Center, this would run in a browser (only Ie unfortunately) and was hosted on a server.. Nowadays it's market share has somewhat dwindled, and there are some new kids on the block. 
One of the more popular tools is that of Microsoft Test Manager, it's big…

What is a PBI?

After my last post, I had the question of what is a PBI... so I thought i'd write a short blog post about what they are and why they are used.

A PBI is an acronym for Product Backlog Item. It is a description of a piece of work that your SCRUM team will develop and deliver. When you have a list of Product Backlog Items, you then refer to that collective list as a Product Backlog.

The product backlog is often prioritised and yourteam will work through each PBI, and release on a regular schedule... I am however going deep into the world of Agile development, which isn't entirely what this post is about, so I will stop myself now.

A Product Backlog Item is made up of the following:

Title - This is often a one liner that gives the team an idea of what the PBI is about, although it can just be an ID for the item and the team work off of that.

Description - Breaks down the PBI in a bit more detail, and can be written in any style, however I prefer it to be written as follows: 

By writin…

Dealing with Selenium WebDriver Driver.Quit crashes (Where chromedriver.exe is left open)

We recently came across a problem with Selenium not quitting the webdriver and this would then lock a file that was needed on the build server to run the builds.

We were using Driver.Quit() but this sometimes failed and would leave chromedriver.exe running. I looked around and found this was a common issue that many people were having. We (I say we, as we came to the solution through paired programming), came up with the following, that would encapsulate the driver.quit inside a task and if this task takes longer than 10 seconds, then it will clean up any processes started by the current process, in the case of the issue on the build server, it would kill any process started by Nunit.

        public static void AfterTestRun()
            var nativeDriverQuit = Task.Factory.StartNew(() => Driver.Quit());
            if (!nativeDriverQuit.Wait(TimeSpan.FromSeconds(10)))

        private s…