Skip to main content

What I love about QA and Testing....

Many people are unfortunate enough to be in a job that they don't like, I won't use the word hate, as that's a strong word, but I'm sure it applies to some people.

I'm lucky, in that when it boils down to it, I do enjoy doing what I do, I enjoy coming to work (and not just to get out the house!) I recently spent time off from work for 3 and a bit weeks, I must say I missed work, I missed the routine, but not only that I missed the people, the actual work I do, the challenges and just keeping my brain active. Sure enough we have bad days where we don't want to come back to work, and maybe the fact that I enjoy QA so much is about the environment I am in, and the people I work with, but I'm lucky to have worked in a number of places and enjoyed almost every one for different reasons.

Drilling down into specifics, "Testing and QA", I thought what is it I love about it?

Hence this blog post....

When I first started out in testing about 6 years ago now, I thought this is great I enjoy breaking stuff, so when people asked me why I want to be a tester, that was pretty much the answer I gave. Nowadays, it's a little more complex than that, as I have come to understand the role that QA play in a business, and how it's really not just about "breaking stuff".

This is in no particular order, so what do I now love about testing? What makes me want to be a tester? Firstly, I think it's the challenge of taking something that the business want and almost looking after it from inception to implementation, making sure it is exactly what was asked for, this involves communicating with people and building up a rapport with a number of people which I thoroughly enjoy.

Secondly, there's the challenging aspect, it's not just about doing repetitive testing tasks, there's the challenge of automating whatever we can, and improving our processes across the organisation. I enjoy looking back and thinking what I did there made a big difference, for instance I've blogged about it in the past, but the Question and Answer forum I implemented, and I really think it's starting to make a difference in how we operate as QA in our company, and I strongly recommend similar implementations for yourselves. Or writing an automated test that can perform something that would take hours in minutes... there's a real kick from things like that.

Thirdly, there's the position that you as a tester are in, you get to find problems in code that otherwise would have gone unnoticed, and it's strangely satisfying when you do find a bug or a problem that nobody else has thought about, it's even better when these problems are found out earlier!

Finally, I think that as a QA we get to try so many different types of technology, we get to explore different types of testing, it's not just about running tests, far from it, we are a beacon of system domain knowledge, of tooling knowledge, and I don't think there's a similar role in IT that offers this wide breadth of activities.

So there you go, yes I do love breaking things, providing it's not something I own... but what I love about QA and Testing is far more than that, and I hope that you agree. What is it that you love about testing? What keeps you coming back day after day?


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.