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!

Comments

Post a Comment

Popular posts from this blog

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.

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

        private s…

Famous Movie Quotes applied to Software Engineering - Jaws

You're gonna need a bigger boat? How can that relate to Engineering?

Firstly, let me ashamedly admit, that I've never seen the whole of Jaws all the way through. It's on my list of films to watch, but whether I get round to it, is another matter!



Anyway, to apply this to engineering, it's almost like "you're gonna need more testers/developers"...

We hear this all too often when trying to push releases out the door, let's throw men at it... However, as we all know, a bigger boat/more men... isn't always the answer, it's not a guarantee of quality, or even a guarantee of getting things done quicker.

If you have a task that will take 2 hours, simply having 2 people work on it doesn't mean that it is halved, in fact often, the time taken to do the task remains at 2 hours, but the maintainability and the knowledge around that area is increased, so it's a price, in my opinion that is often worth paying.