Skip to main content

Becoming a better Tester... One day at at a time...

We can all become better testers, only some of us lack motivation, or some of us have the motivation but just tend to lose interest...

One way we can tackle this, is by attempting to become a better tester one day at a time.

It's much easier to tackle each day, and do something each day that makes you a better tester, than it is to say in 1 month I want to be a better tester.  Firstly, it's hard to define how you can become a better tester, but for me, one thing that would make me a better tester is to read more blogs and learn from experiences of others. With this in mind, I've made it a challenge to read at least 2 blogs a day from a testing blog feed.

This is far easier than if I had set a goal to read 60 blogs a month for instance, it's also more manageable. If I don't do it one day, it's not the end of the world, but it's important to not lose heart.

Also, I find it good to establish a daily habit, I like to read 2 blogs en route to work on a morning, by having a daily habit, it enforces positive behaviour.

You obviously won't enjoy every blog post that you read, but once you get a feel for what blogs you like, then you can subscribe to them and read them as part of this regular reading session.

I understand that not everyone has time to read blogs on their commute, but even during a lunch break, it doesn't matter, what's important is the routine and setting side time to do this, and to help you become a better tester.

Other things that might be interesting and to help you become a better tester could be:


  • Start up a blog and post once a week/2 weeks/month (it's up to you and how you feel about writing)
  • Become more involved in the QA Community and reply to discussions on the various outlets there are (linkedin, Software Testing Club etc.)
  • Start mini projects for yourself (e.g. I've recently started one using Watin to test a website)
There really are many more, and I wouldn't like to say you should do this, as I do believe this is something that is down to the individual, and it's no point me saying you should do this if you don't really believe it will make you a better tester. :)


Comments

  1. Nice post, Thanks for sharing.

    Srinivas Kadiyala
    @srinivasskc

    ReplyDelete
  2. What type of project / attempt are you making with Watin?

    ReplyDelete
    Replies
    1. Hey, early says at the moment. Just getting it to interact with a website and do some basic tests with it. Once I've got to grips with it then I'll look at pushing it further etc.

      The website I've started to use is easyJet altho I may change it to asos so I can have more interactive tests with databases etc in our test environment.

      Delete
  3. This comment has been removed by the author.

    ReplyDelete
  4. Nice read!

    Thanks,
    www.f14testing.com

    ReplyDelete

Post a Comment

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

QA is Awesome!

No real point to this post other than I have had the song stuck in my head and figured I could change it slightly and quite easily make QA is Awesome! Oh and I haven't even seen the movie all the way through! But for some reason that song is incredibly catchy! Not much point to this post in fact, just thought I'd put it out there :)

Measuring QA Key Skills and Competencies

I have been thinking about how I can help encourage self improvement within my team, as I understand it, everyone wants to improve, it's just that often there are a number of things that hold people back. I believe one of these things that hold people back are around identifying skills that they are perhaps weak in or that they could/should improve on. So I thought about how I can help tackle that problem. One solution that I want to try with people is to identify the key skills for a QA, what key skills should every QA have, or at least what key skills make up a good QA? If I can identify these then I can start helping people identify if they are lacking in an area. Sure there is a competency matrix that we have, but it has things like "An excellent understanding of XXX", it's often very difficult to quantify what an excellent understanding actually is. So I sat down and came up with the following key skills: OOP Test Documentation Manual Testing Automated...