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


Labels:

Comments

  1. Srinivas Kadiyala30 September 2013 at 03:59

    Nice post, Thanks for sharing.

    Srinivas Kadiyala
    @srinivasskc

    ReplyDelete
  2. Chris Kenst30 September 2013 at 21:03

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

    ReplyDelete
    Replies
    1. Gareth Waterhouse1 October 2013 at 00:22

      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. F14 Team3 October 2013 at 08:00

    This comment has been removed by the author.

    ReplyDelete
  4. F14 Team3 October 2013 at 08:02

    Nice read!

    Thanks,
    www.f14testing.com

    ReplyDelete

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