Skip to main content

What makes a QA so happy!?

Here's an interesting statistic for you (granted from the USA):

When I stumbled upon this article, I had to read the list twice, really? Being a QA Engineer is the second happiest job!? Someone had better tell that to some people I work with... I joke ;)

What is it that makes this job so happy then?
To me, it's the challenge of learning new things on a constant basis, the past few weeks have been spent trying to get my head around Espresso an automation API from Google for Android apps, I haven't spent as much time as I would have liked with it, but it's definitely challenging, and very rewarding. If I get to spend a whole day on it, then that does make me happy, so there's that I suppose.

Then there's the opportunities to constantly try and think of better ways of doing things, improving how we test so we can spend more time well, testing. It's rewarding coming up with tools or processes that improve peoples work life, just over a month ago I wrote a small program that would update a number of acceptance tests against a PBI in TFS, to save my team from doing it manually, things like that make me happy, knowing they can spend less time doing laborious tasks and more time doing what they enjoy.. Testing.

There's also the argument that regardless what happens, if you have a deployment to a test environment that isn't working, then you've found bugs, you've found issues, you can try and fix it... or if it is finally working, then great! You've got it working. Eric Jacobsen describes it a bit better here (and also the inspiration for this blog post)....

There's also the non technical side of things, being involved in communications from the start of projects, finding out what is going to happen, has this been thought of, really analysing what it is that is going to be developed. So working with a wide array of people, Business Analysts, Developers, Product Owners, Development Managers, you get to talk to so many people and you talk to them on different levels, which is really rewarding, and does make me happy.

So there you have it, these are just some of the things that make me happy, I'm definitely interested in what makes you happy as a tester? And also interested as to what makes Database Administrators so happy!? I think I might go and ask that question now!!!


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.

        public static void AfterTestRun()
            var nativeDriverQuit = Task.Factory.StartNew(() => Driver.Quit());
            if (!nativeDriverQuit.Wait(TimeSpan.FromSeconds(10)))

        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.