Skip to main content

Setting up a company QA forum/Wiki

I've recently looked into creating a QA forum, at a request of a number of team members, where members of the QA community inside where I work can post questions or blog posts and share them with others.

The benefits of using something like this over email is that it keeps everything in one place, it stores the questions for ever, so if we have new starters and they have a question they can look at these sites first before sending out an email.

I've suggested OSQA as the question exchange software and we are just going to use a standard wiki for the blog post /information storage.

I got asked how can we ensure that its kept up to date? As it will only really be useful if it is kept up to date.

The simple answer is, that if it's not kept up to date then obviously people aren't using it so it's not that much of an issue if that is the case. If people are using it consistently then it should in theory stay up to date and be an excellent source of information for new starters and older heads! 


I will keep you up to date with its success (or lack of)  over the next coming months! 
Labels:

Comments

  1. halperinko20 August 2013 at 21:57

    If its only for internal issues - then it make sense, if its for general issues - I would direct to one of the community forums.
    We also use a network directory of "HowTo", where we keep different internal usage instructions in MS-Word or TXT format - this reduces the need to elaborate common instructions in STD.
    Might be easier to save E-Mails as text rather than export into wiki, and probably easier to maintain.
    @halperinko - Kobi Halperin

    ReplyDelete
    Replies
    1. Gareth Waterhouse21 August 2013 at 00:22

      Hey,

      This will only be for internal issues that are specific to our systems and their architecture. We'll also have a wiki which will have a few things on...

      But you're right, for general issues, community forums are definitely the way forward.

      Delete
  2. Fefal17 October 2013 at 08:05

    I really don't get the point to have QA forum wiki. It will be great to display a sample to understand the idea over this, for the QA members.
    Currently we have a wiki but we don't use it much...

    ReplyDelete
  3. Gareth Waterhouse18 October 2013 at 00:23

    We have a wiki and this QA forum. It's effectively an online message board where people can post questions they have about ASOS systems that someone in QA might be able to answer, there's also a karma aspect in that people that give good answers receive upvotes (kind of like reddit). It's better than emailing all of QA to ask a question as often the emails will get lost over time, whereas this way we have a storage for all the questions that might be asked, and the search functionality is pretty good as it makes use of tags etc. If you often have people asking you questions and sometimes it's the same question then I'd highly recommend something like this :)

    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...
15 comments
Read more

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...
Post a Comment
Read more

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...
Post a Comment
Read more