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?

Comments

Popular posts from this blog

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

How to manage resources within new teams?

Working where I work we are constantly spinning up new teams to take on new workloads as business come up with new demands and new features they want developed and tested. The problem with this is how do we ensure the work of the newly spun up team is of sufficient quality. One method is by taking people from other established teams and placing them on the new team. This works great for the new team, but unfortunately it will oftenl eave the established team lacking in a resource whilst they try and fill the gap left by the person who has left. We are seeing this often with our offshore teams, it can be damaging to the team structure and the teams velocity, but try as I might, I can't think of another way around it. It's far easier to take 1 person from a team that is established than it is to build a whole new team from scratch. At least by leaving the core of a team in place, you should be guaranteeing that the new team are aware of any coding standards or any QA standard...

Considerations when creating automated tests

We recently released to a number of teams our automated regression pack that has been worked on over the past few months. This regression pack tests legacy code, but contains a large number of tests.  As a bit of background, a number of teams are working on new solutions whilst some are still working on legacy code. With this in mind we constructed an email with a list of guidelines when creating new tests that need to be added to this regression pack.  I figured that these can be quite broad so should apply for any organisation, so thought it would make an interesting blog post...  So here goes,  when creating automated tests, it's important to consider and adhere to the following: - Think about data . The tests need to retrieve or set the data they need without any manual intervention - This should help them be more robust and easier to run without manual intervention. - The tests need to be idempotent - By making it so that each test is standalone and does...