Skip to main content

Key characteristics that help me be a good tester

I recently took part in a PI assessment, for those that don't know what a PI assessment is, it's a behavioural assessment, the PI stands for Predictive Index. It asked 2 questions, and asked you to tick words that describe how you feel in reference to the questions. 

The questions were (something like) :

- Describe how you view yourself
- Describe how you behave in your work environment

You then had to tick as many words that you felt applied to the question. 

I'm going to take the results of the assessment and hopefully try and explain how this applies to testing and how it makes me a good tester, also how it highlights things that I feel that I need to work on.

The first part is to analyse your natural behaviours:

·         You are a team orientated person, co-operative and agreeable you seek harmony where you can. - I think this helps especially in working in an agile environment, where we work in such a close knit team, it's important to be co-operative and a team orientated person to help get work done.
·         You are sociable, easy-going and work best when you are in a familiar environment/team. 
·         You are trusting of others so feel comfortable delegating work/authority – only when are familiar with them, it takes time before you truly trust people. Your empathy to others means you often unselfishly show interest in others, you teach and share ideas/thoughts openly and freely. I think that this helps in mentoring others and develop other individuals, so not really testing related, but more about being a senior member of a team. Perhaps I could work on the trust issue, in that I could be more open and delegate tasks more freely, so I will look to work on this.
·         You are patient, calm and consistent which makes you dependable to others. This is useful when being a tester, as the last thing you want to do is panic when things could/can go wrong! A calming influence can help teams stay calm and working towards a goal.
·         You tend to avoid risks, preferring to do things by the book I would possibly disagree with this to a degree, I do tend to avoid risks, but I don't always perhaps do things by the book unless it's something I believe in. 
-  this is due to your attention to detail. You are accurate and careful with detail – meaning you can sometimes be cautious/conservative. I think this is always good for a tester to have! :)
·         When making decisions, you are very objective – needing all the facts in order to make a well balanced decision – some may say that your decisions are black or white. This comes in handy when coming up with a risk based approach to testing, when deciding what tests to run. I do disagree slightly with the decisions being black and white, I am open to negotiating!
·         You are motivated by encouragement, team recognition and freedom from risky decisions.
·         You are happier in a stable work environment and work better where there is certainty and you have specific knowledge of the job you are doing. I definitely agree with this, and this is possibly one of the reasons I haven't gone contracting yet, I like knowing what I am going to be doing, I like being a part of a team. 
·         The PI also suggest that you have a rather low mental energy – meaning you tend to burn out if you don’t get regular breaks from what you are doing.

Next is to look at your self-concept – this is essentially how you are behaving in your current environment. This shows that:
·         You are perhaps working at a more intense/faster pace than you would naturally. You are dealing with more variety and change than you would prefer. Suggesting that you are putting more pressure on yourself. This was weird as I've just changed roles, so is definitely something that I am dealing with at the minute, I'd like to think I'm coping though! And not putting too much pressure on myself!
·         Whilst you like detail, this suggests you are maybe having to be more detail orientated than you would normally. You are having to adjust to a more structured and controlled environment and as such being more formal and more individually involved – which goes against your natural team style. Again, with the new role, the team do seem more structured and it is a more controlled environment to what I was used to before, but I wouldn't say this is a negative, but it is strange not being a part of such a strong team.
·         Due to the adaptations you are making, this suggests that your morale is slightly low. I wouldn't say my morale is low, I'm enjoying what I am doing, there are things that I am missing, such as the team ethic, but I enjoy the challenge of the day to day role.

So that's pretty much it. I think it was pretty eye opening, and I do agree with the vast majority of it, and some of the characteristics, as discussed above do help me excel in testing.

What characteristics do you think are good to have as a tester? I often see people say testers need to be negative, but I strongly disagree with this, we don't have to be negative, we can be positive, but so long as we are objective and not positive without due cause!


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…