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

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