Skip to main content

Measuring QA Key Skills and Competencies

I have been thinking about how I can help encourage self improvement within my team, as I understand it, everyone wants to improve, it's just that often there are a number of things that hold people back.

I believe one of these things that hold people back are around identifying skills that they are perhaps weak in or that they could/should improve on. So I thought about how I can help tackle that problem.

One solution that I want to try with people is to identify the key skills for a QA, what key skills should every QA have, or at least what key skills make up a good QA? If I can identify these then I can start helping people identify if they are lacking in an area. Sure there is a competency matrix that we have, but it has things like "An excellent understanding of XXX", it's often very difficult to quantify what an excellent understanding actually is.

So I sat down and came up with the following key skills:
  • OOP
  • Test Documentation
  • Manual Testing
  • Automated Testing
  • Performance Testing
  • Security Testing
  • Operational Testing
  • Tool Usage
  • Cross Browser Testing
  • Automation Pyramid
  • SQL
  • Test Data
  • Communication Skills
  • Mobile
I'm sure there may be more, so please feel free to comment and suggest some to me. However, these will definitely do as a starting point and for the purpose of this exercise.

Secondly, I thought it's easy to go through and say I know a bit about SQL, I know a bit about Services/API Testing so I don't really need to learn them. So I thought about the following, sitting down with each QA member and discussing with them how strong they are, and trying to come up with a score out of 10 on how they would rate their knowledge, I would then put this into a radar graph to achieve an overall view of their skills as a QA.



As you can see I have tried to do it for myself, it's difficult coming up with scores, so it's by no means final as ideally I would discuss these with my manager and come to an agreement, but I think it is easy to see the areas that I need to improve on. I have also aligned these to the core competencies matrix that we have adopted, so it ties into helping people develop themselves with an eye for a promotion etc.

The next step is coming up with actions on how we can improve the above, but I will save that for a separate post!



Labels:

Comments

  1. Anonymous4 April 2014 at 14:04

    This is a great list! What about adding testing to meet accessibility standards? Our team here at Pixo (pixotech.com) strives to meet accessibility standards (especially for our higher ed clients) so we do in-depth testing for that as well. It's a bit of an undertaking but well worth the effort for those with disabilities to be able to use our websites.

    ReplyDelete
    Replies
    1. Gareth Waterhouse7 April 2014 at 04:30

      That's a good idea! Like I said this isn't a definitive list, so any suggestions are welcome. Where I work currently there is a drive to start performing accessibility testing, and in fact I got the team to do presentations on areas of testing and accessibility testing was one of them! Thanks!

      Delete
  2. calvinewers4 September 2017 at 22:23

    Life cycle is very well explained in tabular format... really helpful for the one's who are looking ahead to automate their manual testing process. Load Test Website

    ReplyDelete

Post a Comment

Popular posts from this blog

Treating Test Code as Production Code

It's important when writing automated tests to remember that the code you write should be up to production standards, meaning any conventions that you have in place should be adhered to and that it should follow good design patterns. Too many people often say why does it have to be as good as production code, it's "Only" a test, so long as it passes then that's fine... To answer this we need to look at why we want our tests to be written in such a structured and efficient manner: - Maintainability - by making the test code structured and efficient, it becomes far easier to maintain and in doing so changes in the future can happen quickly as the test isn't linked to anything that it shouldn't be and it's easy to understand for a new set of eyes. - Durability - Again by making the tests structured they should be resistant to changes, if you change a variable name for instance then it shouldn't effect the unit test unless it absolutely has to....
1 comment
Read more

Testers: Be more like a Super-Villain!

Who doesn't love a Super Hero? Talk to my son, and he'll tell you how much he loves them, talk to many adults and they'll say the same! Deep down, we all love to be the Super Hero, we all want to save the day! However, I want to talk about the flip side of Super Heroes, the Super Villains... I often play Imaginext with my son, and I (unfortunately?) am nearly always the Super Villain! Be it Lex Luthor, Joker, Two Face, Mr Freeze or The Riddler! These are all great characters and great Super Villains, but why would I want to write about Super Villains? A while ago where I worked, we had a few Super Heroes, people who would be able to come in and "fix" things that had broken and help deliver projects on time. We then shifted, we decided to do away with the Super Hero culture and try and prevent from being in that position in the first place, whilst we didn't go as far as wanting to hire Super Villains, it's definitely a story that has stuck with me and t...
2 comments
Read more

Using BDD and gherkinising your Acceptance Tests

In my post Testing of Automated tests , I mention about a BDD framework which involves using BDD to drive your acceptance tests. BDD stands for Behaviour Driven Development.  One effective method of writing BDD tests are by using a format known as Gherkin language. These consist of Given, When, Thens. The main advantage of the gherkin language is that it's readable by the business, and in an ideal world forms part of the Conditions of Acceptance around a PBI. Also, using a Visual Studio plugin of SpecFlow , you can integrate your Gherkinised COAs into your solution with feature files, and then drive the automated tests, however, for this post I will focus solely on how to effectively gherkinise your acceptance tests. A Feature file consists of a feature outline, which details what the feature file is testing followed by Scenarios and examples (parameters).  The BDD scenarios are made up of a Given, When, Then... These are effectively an initial state (Given), an action (W...
6 comments
Read more