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

Coding something simple.... or not! Taking a screenshot on error using Selenium WebDriver

I recently wrote a little function that takes a screenshot at the end of a test if it has errored. What sounded very simple at the start turned out to be quite a bit of work, and quite a few lines of code to handle certain scenarios! It's now over 50 lines of code! I'll start with what I had at the beginning, this was to simply take a screenshot in the working directory, we are using SpecFlow and Selenium to run the tests, so we are going to check if the ScenarioContext.Current.TestError isn't null, if it is, then using Selenium, take a screenshot (note the below code is a simplified version of what I had at the beginning). [AfterScenario]         public static void TakeScreenShotOnError()         {             if (ScenarioContext.Current.TestError == null) return;             var screenshotDriver = Driver as ITakesScreenshot;             if (screenshotD...

How to manage resources within new teams?

Working where I work we are constantly spinning up new teams to take on new workloads as business come up with new demands and new features they want developed and tested. The problem with this is how do we ensure the work of the newly spun up team is of sufficient quality. One method is by taking people from other established teams and placing them on the new team. This works great for the new team, but unfortunately it will oftenl eave the established team lacking in a resource whilst they try and fill the gap left by the person who has left. We are seeing this often with our offshore teams, it can be damaging to the team structure and the teams velocity, but try as I might, I can't think of another way around it. It's far easier to take 1 person from a team that is established than it is to build a whole new team from scratch. At least by leaving the core of a team in place, you should be guaranteeing that the new team are aware of any coding standards or any QA standard...

Considerations when creating automated tests

We recently released to a number of teams our automated regression pack that has been worked on over the past few months. This regression pack tests legacy code, but contains a large number of tests.  As a bit of background, a number of teams are working on new solutions whilst some are still working on legacy code. With this in mind we constructed an email with a list of guidelines when creating new tests that need to be added to this regression pack.  I figured that these can be quite broad so should apply for any organisation, so thought it would make an interesting blog post...  So here goes,  when creating automated tests, it's important to consider and adhere to the following: - Think about data . The tests need to retrieve or set the data they need without any manual intervention - This should help them be more robust and easier to run without manual intervention. - The tests need to be idempotent - By making it so that each test is standalone and does...