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?

Comments

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

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…

Famous Movie Quotes applied to Software Engineering - Jaws

You're gonna need a bigger boat? How can that relate to Engineering?

Firstly, let me ashamedly admit, that I've never seen the whole of Jaws all the way through. It's on my list of films to watch, but whether I get round to it, is another matter!



Anyway, to apply this to engineering, it's almost like "you're gonna need more testers/developers"...

We hear this all too often when trying to push releases out the door, let's throw men at it... However, as we all know, a bigger boat/more men... isn't always the answer, it's not a guarantee of quality, or even a guarantee of getting things done quicker.

If you have a task that will take 2 hours, simply having 2 people work on it doesn't mean that it is halved, in fact often, the time taken to do the task remains at 2 hours, but the maintainability and the knowledge around that area is increased, so it's a price, in my opinion that is often worth paying.