Skip to main content

Raising your profile in QA

I've been told in the past that I need to raise my profile within the QA community, not just in work but outside of work as well. I need to be more vocal and speak out more in work, and get people to know me, which I have started to do and am quite enjoying it.

In light of this I want to offer advice to other people about how they can raise their profile within the QA community outside of their workplace, as well as in their workplace, as raising one will hopefully raise the other.

Firstly, I never thought I would get into this blogging malarkey  but I can definitely say it has helped make me a better QA. Someone once said to me that blogging is useful as it might help someone learn something, and if not, then it can help you and is a good point of reference if you ever need to look back on anything. I also find it quite therapeutic by writing out about how I feel about certain aspects of my job. This will help raise your profile inside and outside of work, share your blog on twitter, google+ and facebook, share it within your work place, and share it with communities that you are a part of..

So I mentioned about communities, I have recently joined up to the Software Testing Club, and can say my initial thoughts are that it's a very good community to be a part of. There's links to an abundance of blog posts, links to testing meetups and a very active discussion forum. Hopefully I can contribute there and become an active member.

I've decided that I also need to try and attend testing meetups, which is hard for me, as I do value time at home with my son, and find that these testing meetups happen on evenings etc. However, I am going to try and attend meetups once a month going forward, I think the hardest thing will be attending the first meetup, hopefully once I've attended one, it'll become a lot easier....

The 2 I mentioned above, will probably mainly help your standing within the outside world of QA, in order to increase your standing within the QA team, you need to be vocal in meetings, you need to be opinionated and drive to improve processes. People will start listening to you, and at least asking for your opinion on things.

You can also follow QA professionals on twitter, they'll often post links to blogs that they've written or read, and can be a good point of reference if you have any questions around your role, and more often than not they'd be happy to help (I know I would :) ).

Also, if you find anything interesting that will help you do your job, share it around, be it on twitter, in a blog post, or emailing the QA team in your IT department, it doesn't even have to be restricted to your QA team, send it to anyone you think would benefit from it. 

Finally, you should read and comment on other peoples blogs, this will benefit you in 2 ways, it will improve your knowledge of the QA field and hopefully people will start looking back at your blog and notice you.

Can anyone think of any other ways that you can improve your profile within the QA community both inside and outside of your work place? It's a long process though, so don't expect results overnight.

Comments

  1. Glad to see you becoming part of the community - it's pretty much the route I followed
    Lurking on forums then asking questions then helping answer questions
    Commented on blogs then started my own blog
    Active on Twitter
    Helped start and run Tester Meetups - I understand your point about wanting family time but meetups are usually just once a month

    As you note at the end, it's a long process so keep it going
    It's also something that *you* want to be doing, if you're trying to do it because you've been told to or because you think it's something you should be doing then it will show. So, why are you trying to raise your profile ?
    :)

    ReplyDelete
    Replies
    1. To be honest, it's making me better at my job, I'm also really enjoying it, the blogging, the learning new things and just getting involved in something outside of my work. If I have 5 minutes spare I'll have a look at a blog or add something to my blog, whereas before I'd probably just browse the net! I've also realised that I have a lot to share! :)

      Delete

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