Skip to main content

Mindset of a Tester

In light of another flop at a major championship for an English national team (Under 21s European Championship), and reading the following article on sports psychology and what sports professionals can do to be at the top of their game, it got me thinking what can a tester do to stay at the top of their game? What type of mindset is important for a tester?

 I find that all too often, people in testing just glide through without trying to further themselves and improve themselves.

 In the article above it highlights 6 ways that a sports professional can maximise their potential through the right mental attitude, I will take these and adapt them so that they can apply to a tester:
Focus on success
Focus on releasing successful software, (if that is the goal of the project), in fact we can make that broader by saying that we should focus on a successful project, and to be a part of that success and try and do everything you can to achieve said success.  Try not to get drawn into focusing on negatives, which leads us nicely to... 

Create a positive self-image
I've mentioned in the past about increasing your profile within QA, but this is slightly different in that it's about creating a positive self image across the company, and perhaps more importantly across your team. If you're positive yourself, then you'll find people will be positive towards you and your team, and positivity breeds success, so it does kind of relate to the first point above.

Define and work towards goals
These goals can be personal goals, or team goals. For personal goals they can be anything from driving some method of testing forward within your company (for instance Exploratory Testing) or for team goals, they can be to drive TDD as a team within the company and try and help other teams adopt the process.

Take personal responsibility
You need to be responsible for your actions within your team, if you make a mistake then hold your hands up, people are much more likely to forgive and forget if you are honest with them from the start.

Pursue self-improvement
I love a David Brent quote which is as follows "nothing ever changes by staying the same" and that is blatantly obvious, but it's surprising how many people expect changes to happen or improvements to happen when they haven't actually changed anything about themselves. If you see a weakness in your skills then drive to improve it, if you're not good at communicating then look at ways you can improve it, or technical skills can be improved easily by taking courses online in your spare time.

Learn from others
Perhaps one of the most important things here, and that is we need to learn from others within our team, within our company and within the wider QA community. On the flip side, we ourselves need to be open about what we know, and share the knowledge, otherwise nobody learns anything from anybody and that's just not a very healthy environment to be in.

Can you think of anymore mental attitudes you can adopt to help become a better tester? or a better professional as looking at the list, I believe it can be adapted to any profession, (as I have done..) and not just sports or testing!
Labels:

Comments

Post a Comment

Popular posts from this blog

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....
1 comment
Read more

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...
2 comments
Read more

Using BDD and gherkinising your Acceptance Tests

In my post Testing of Automated tests , I mention about a BDD framework which involves using BDD to drive your acceptance tests. BDD stands for Behaviour Driven Development.  One effective method of writing BDD tests are by using a format known as Gherkin language. These consist of Given, When, Thens. The main advantage of the gherkin language is that it's readable by the business, and in an ideal world forms part of the Conditions of Acceptance around a PBI. Also, using a Visual Studio plugin of SpecFlow , you can integrate your Gherkinised COAs into your solution with feature files, and then drive the automated tests, however, for this post I will focus solely on how to effectively gherkinise your acceptance tests. A Feature file consists of a feature outline, which details what the feature file is testing followed by Scenarios and examples (parameters).  The BDD scenarios are made up of a Given, When, Then... These are effectively an initial state (Given), an action (W...
6 comments
Read more