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!



Comments

Popular posts from this blog

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 t...

Treating Test Code as Production Code

It's important when writing automated tests to remember that the code you write should be up to production standards, meaning any conventions that you have in place should be adhered to and that it should follow good design patterns. Too many people often say why does it have to be as good as production code, it's "Only" a test, so long as it passes then that's fine... To answer this we need to look at why we want our tests to be written in such a structured and efficient manner: - Maintainability - by making the test code structured and efficient, it becomes far easier to maintain and in doing so changes in the future can happen quickly as the test isn't linked to anything that it shouldn't be and it's easy to understand for a new set of eyes. - Durability - Again by making the tests structured they should be resistant to changes, if you change a variable name for instance then it shouldn't effect the unit test unless it absolutely has to....

Tech Develops - A day dedicated to YOU!

Working in Tech, it can be difficult to find the time to further improve yourself, you're focused a lot on delivery, and it can be hard to drag yourself away from it and spend time on delivering an improved you. This is why some companies are starting to have time dedicated to your personal development, where people drop tools and do a personal project or watch some tutorials. Luckily working at ASOS we get the last Friday of every month to focus on this! Last Friday we held what we call a "Tech Develops" day, where as an employee of ASOS and working in Technology, In the week running up to it we decided it would be a good idea to have a platform where people could stand up and perform a 99 Second Talk about anything they please. We had 12 people sign up to it, and we had talks ranging from the technical (Git-Bisect) to a Conference review (UKStar). The first talk was an informative talk about Git Bisect and how it's used and why because of it, it's import...