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!!!
Labels:

Comments

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 follow...
68 comments
Read more

Coding something simple.... or not! Taking a screenshot on error using Selenium WebDriver

I recently wrote a little function that takes a screenshot at the end of a test if it has errored. What sounded very simple at the start turned out to be quite a bit of work, and quite a few lines of code to handle certain scenarios! It's now over 50 lines of code! I'll start with what I had at the beginning, this was to simply take a screenshot in the working directory, we are using SpecFlow and Selenium to run the tests, so we are going to check if the ScenarioContext.Current.TestError isn't null, if it is, then using Selenium, take a screenshot (note the below code is a simplified version of what I had at the beginning). [AfterScenario]         public static void TakeScreenShotOnError()         {             if (ScenarioContext.Current.TestError == null) return;             var screenshotDriver = Driver as ITakesScreenshot;             if (screenshotD...
14 comments
Read more

The Stickman Tester... The full version complete with deleted "scenes"!

As some of you may have seen, a little while ago I performed a 99 second talk on the Stickman Tester for the Ministry of Testing. Owing to the fact that it had to be 99 seconds, this unfortunately meant that a verse was left out in order to keep it within the time frame! It's only now that I have found the time to put the deleted verse/scene back in, and re-record it and upload it! (It's now a 120 second talk!) It talks about a testers journey in an Agile team, about how not everybody has it as good as others, and basically talks about not giving up, keep searching, or trying to change your role to make it what you want it to be. Anyway, here it is, in all it's glory. Hope you enjoy it!
15 comments
Read more