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

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