Skip to main content

Be the Positive Tester!

Being positive is becoming increasingly difficult, in a world where negativity is all around us in the form of News reports, just looking at a popular news feed a large portion of the articles are of a negative nature or in a negative tone, then there's the fact that people love to moan or gossip about someone not doing what they are supposed to do and similarly people are far more likely to leave a negative review for a product or service than they are a positive one! So how can I be more positive and why does it matter? All I do is test?

Firstly, never ever say or think "All I do is test", you do so much more, and we all do so much more, it's about showing everyone just how awesome we can be and how great we are!

Secondly, why does it matter? Well a Tester can have every attribute that is needed to be a Tester, but if they have a negative attitude it can all be for nothing. I've found that by merely having  a positive attidue it can take an Okay Tester and turn them into a bloody good Tester! Dumbledore said it best with:

"It is our choices, that show what we truly are, far more than our abilities"

So yes, Dumbledore is fictional...but it's a true statement, and one that fits nicely in to this blog post!

So why does it matter? Well, positivity is very contagious, I've worked with positive people, people who are insanely positive, and it rubs off on me, in fact it rubs off on everyone around them, so if you're positive and working in a team, by being the positive person it will help the team be more positive and in turn make them happier! Let's not forget that Happiness more often than not equates to success.

Also if you are happy and positive in negative situations, then people are more willing to listen to and help someone who comes to them with solutions to problems rather than just moaning about the current situation and not really be willing to do anything about it! Persuasion is an important skill, one that is often overlooked, postivity feeds into that, persuading someone is far easier when you are positive!

So, it's all very well talking about why it's important to be positive, but unfortunately, like most things, it's just not as easy as that, we can't just flick a switch and instantly become more positive... What we can do is do little things that will hopefully all feed into making you feel and be more positive!

One of the things that I like to do is to spend time reflecting on the day, this doesn't have to be at the end of the day, it can just as easily be at certain points in the day, look back and thing about what's gone well so far, what have I enjoyed about the day and what is happening in the near future that I'm looking forward to. This isn't necessarily a physical reflection, just by thinking about these things makes me realise that success happens far more often that you might think!

We can also set ourselves goals, not just daily goals, they can be weekly or even longer term, what are some things I want to achieve? One goal that I have wanted to achieve was to speak at a public conference, I achieved that this year, and am looking at doing it more often in the future, by having this long term goal I can look at small things I can do to help me achieve it. I know it's cliche, but it's good to know where you want to be in 5 years time, so you can then work towards it.

People often think of Testers as negative people, we love to break things and point out the negative things about software, but we need to celebrate when these things happen, it's far better to find a bug in test than in production! We also need to celebrate and learn from our failures, this isn't always easy, but if we fail fast and learn from it, then is it really a failure? We've learnt something which should be celebrated!

As mentioned earlier as well, we need to look at problems as opportunities, and have solutions ready for any problems we might have... If we don't have enough time to test something, what can we do? Can we do some Risk Based Testing? Or can we work through lunch? Or can the entire team get involved and get it tested?

Finally, just be friendly and enthusiastic, and adopting that positive mindset will follow, especially if you start reflecting and setting yourself achievable goals and actually achieving them! It will make you feel better about yourself as well as make the team feel better and happier! I was watching a TED Talk the other day that we can make ourselves feel more powerful by adopting "Superman" Poses, and I see this being no different we can make ourselves more positive just by reflecting and thinking about what went well and building on that!

Just to summarise the blog post, here's a nice MindMap!



Comments

  1. i'm wondering this articles topics, testing is one life cycle of every product delivery. Development and Maintains always required testing, but doing by tester or developer became as testing !!!

    Software Testing Training in Chennai

    ReplyDelete
  2. Excellent site. A lot of useful info here. I’m sending it to some friends ans also sharing in delicious. And certainly, thanks for your effort! google ads singapore

    ReplyDelete
  3. You can definitely see your expertise in the work you write. The sector hopes for more passionate writers like you who are not afraid to say how they believe. All the time follow your heart. singapore ad

    ReplyDelete
  4. I found your blog site on google and examine just a few of your early posts. Continue to keep up the excellent operate. I just extra up your RSS feed to my MSN News Reader. Looking for ahead to studying extra from you in a while!…
    e commerce singapore

    ReplyDelete

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