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! 

Comments

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

What is a PBI?

After my last post, I had the question of what is a PBI... so I thought i'd write a short blog post about what they are and why they are used.

A PBI is an acronym for Product Backlog Item. It is a description of a piece of work that your SCRUM team will develop and deliver. When you have a list of Product Backlog Items, you then refer to that collective list as a Product Backlog.

The product backlog is often prioritised and yourteam will work through each PBI, and release on a regular schedule... I am however going deep into the world of Agile development, which isn't entirely what this post is about, so I will stop myself now.

A Product Backlog Item is made up of the following:

Title - This is often a one liner that gives the team an idea of what the PBI is about, although it can just be an ID for the item and the team work off of that.

Description - Breaks down the PBI in a bit more detail, and can be written in any style, however I prefer it to be written as follows: 



By writin…

Dealing with Selenium WebDriver Driver.Quit crashes (Where chromedriver.exe is left open)

We recently came across a problem with Selenium not quitting the webdriver and this would then lock a file that was needed on the build server to run the builds.

We were using Driver.Quit() but this sometimes failed and would leave chromedriver.exe running. I looked around and found this was a common issue that many people were having. We (I say we, as we came to the solution through paired programming), came up with the following, that would encapsulate the driver.quit inside a task and if this task takes longer than 10 seconds, then it will clean up any processes started by the current process, in the case of the issue on the build server, it would kill any process started by Nunit.

[AfterTestRun]
        public static void AfterTestRun()
        {
            var nativeDriverQuit = Task.Factory.StartNew(() => Driver.Quit());
            if (!nativeDriverQuit.Wait(TimeSpan.FromSeconds(10)))
            {
                CleanUpProcessByInheritance();
            }
       }

        private s…

Advantages of using Test Management tools

Before I start talking about test management tools, let me clarify what I mean by the term test Management tools...  I am not taking about your office excel program where you store your test cases in. I'm talking about bespoke test Management tools, your quality centers or Microsoft test manager...
In the strict case of the term test Management tool, Microsoft Excel can be used as such, but heck, so could a notepad if used in the right way... For the sake of this blog post I am talking about bespoke test Management tools.
Firstly, what test tools are out there? There are many more out there today than when I first started in QA over 5 years ago. When I started the market was primarily dominated by a tool called Quality Center, this would run in a browser (only Ie unfortunately) and was hosted on a server.. Nowadays it's market share has somewhat dwindled, and there are some new kids on the block. 
One of the more popular tools is that of Microsoft Test Manager, it's big…