Skip to main content

Company QA Community Blog

I'm thinking of creating a QA Community blog in my current workspace, you may ask why? What would be the benefits of this?

I can think of a number of immediate benefits:
- People within the Community will be more aware of what others are doing by their posts on there
- People can more easily learn from one another, I feel that by writing up about something, even in a blog post you learn more about it yourself, and the people reading the blog post will also learn from it
- It will encourage people who possibly hadn't thought about having their own blog to get involved and contribute

There are also benefits for the wider community in that:
- People will read it, and hopefully contribute to it outside of asos and offer insights into what might work better etc.
- People will read it and want to be a part of it, and thus make the company a more attractive place to work

The biggest hurdle I think will be actually getting people to contribute to it, once it is up and running however I will be sure to share it on here, so everyone can look at it! There's also the problem with the content being the view of the QA member who is posting it and not of the bigger company, but that can easily be avoided.

Does anyone else have a company QA Blog? Any advice on getting it to work and be adopted?
Labels:

Comments

  1. John Stevenson22 April 2014 at 05:30

    Hi Gareth

    Our company have something like this already set up. Get in touch with me via twitter (@steveo1967) and I can then provide some contact details so we can discuss this in more detail.

    ReplyDelete
  2. Bart22 April 2014 at 22:25

    We did internal setup a OSQA server (http://www.osqa.net/) as our knowledge 'database', To make people contribute to it, all our internal releases of the software is announced with a mail. In that mail we also mention each time the link to the OSQA server, so that our collegues are aware of it. Of course we also had some kind of presentation of the usage after rolling out that server a few years ago.

    ReplyDelete
  3. saraan3 March 2019 at 06:52

    . I just wrote an incredibly long comment but after I clicked submit my comment didn't show up. Grrrr... well I'm not writing all that over again top digital marketing agencies

    ReplyDelete

Post a Comment

Popular posts from this blog

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

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

Tech Develops - A day dedicated to YOU!

Working in Tech, it can be difficult to find the time to further improve yourself, you're focused a lot on delivery, and it can be hard to drag yourself away from it and spend time on delivering an improved you. This is why some companies are starting to have time dedicated to your personal development, where people drop tools and do a personal project or watch some tutorials. Luckily working at ASOS we get the last Friday of every month to focus on this! Last Friday we held what we call a "Tech Develops" day, where as an employee of ASOS and working in Technology, In the week running up to it we decided it would be a good idea to have a platform where people could stand up and perform a 99 Second Talk about anything they please. We had 12 people sign up to it, and we had talks ranging from the technical (Git-Bisect) to a Conference review (UKStar). The first talk was an informative talk about Git Bisect and how it's used and why because of it, it's import...
3 comments
Read more