Skip to main content

How to go above and beyond in your role as a QA?

I often try and think of ways that I can offer value to my company by going above and beyond that of a standard QA.

Whilst this will vary from company to company, I've decided to list ways that I try and go above and beyond in my company and my role to help out and offer as much value as possible.

These are in no particular order, but here goes:

1 - Share your domain knowledge, whilst this should be a given, all too often this isn't the case. If someone asks for help on a particular subject, help them, don't just say I'll do it and let you know when it's done. If you show them then they will hopefully learn and be able to help others, and become less reliant on you and your time.

2 - Offer your help whenever you can, if you do have an expertise in a particular system, or something you have worked on in the past, when issues arise, don't shy away from offering advice, or offering solutions to problems. This will get your name out there and people will take notice of you.

3 - Read up as much as you can, read and join in communities and share what you learn and apply it to your day to day job. We need to be forward thinking as a QA community, and really drive best practices and try out any methods that you think will offer value to your business/QA department.

4 - Learn your systems, whether it's something you work on regularly or something you only work on sporadically, learn it, you will be able to help others and you will further the overall picture of the system architecture and how it might affect something you are actually working on. All too often, people get pigeon holed into working on one system, and it can be difficult to get out of that. Which may offer value to your company at present, but it won't offer much value in your next role at a new company. A good example of this is currently I know a lot about FredHopper and it's integration with Asos, however, whilst this offers an awful lot of value to my current employers, in the future it won't really do me any favours. So by learning new systems and new skills, which I am currently doing, I offer value to both my employers and also to myself in the future.

5 - Offer support to other teams, if you can offer support to other teams, in anyway possible, be it answering questions or running some tests for them, then you should. It will be appreciated, and teams will be more likely to return the favour.

6 - Learn new skills, I've spoke about this in the past, but all too often people just sit on their laurels and don't learn anything new, thinking they know enough to get where they are, and just lack the drive and ambition to go further. I want to achieve as much as I can in my career, I want to make people proud of me, and want to provide for my family as best I can, to do this, I try and learn new skills as much as I can, as who knows where my career will take me.

None of the above should be limited to the QA department, or even IT, we should offer the business as much value as we can, and why should that be limited to QA/IT?

How do you think you can go above and beyond in your role? What do you do that marks you out as a QA that goes above and beyond?


Comments

  1. Good approach Gareth, I bet that you not only become more valuable to your team, but you also make your job much more interesting.
    You sound like a T-shaped tester, the ones I like to work with. I described T-shaped testers @ http://bit.ly/1dgOFRO if you are interested.

    ReplyDelete
    Replies
    1. Wow that's a really interesting and insightful article! I fully agree with it, and think everyone should strive to be a T shaped tester, especially in an agile world!



      Thanks!

      Delete
  2. good one lots of things to learn from this thanks..

    ReplyDelete
    Replies
    1. Excellent! I hope you can learn and put some of the above into action!

      Good luck!

      Delete
  3. This blog is so precious. A gift for the blog readers.
    resumeyard.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.