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

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.