Skip to main content

#30DaysOfTesting update! Day 4 - Share a Testing Blog!

So it's been a tad difficult to do the challenges over the weekend (had school fete, kids parties etc!), so I've changed things up slightly and am going to do challenge 2, 3 and 4 today...

So, first things first, a photo of work...

Whilst this wasn't today, the premise is still the same, this was of a QA++ training session, where we were going through YAGNI and DRY principles (You Aint Gonna Need It and Don't Repeat Yourself) with regards to Software Development, however these principles can easily be applied to Testing, if you don't need to Test for something then don't do it and if you communicate effectively then there's no need to repeat yourself, so it's an art for sure!

For the listening to the Testing Podcast, I'm going to listen to the latest Testing in The Pub Episode on my way home from work, so will no doubt include that in my next update!

And finally, to share a Testing Blog with a Non Testing Person... I've chosen this one: "Testers get out of the Quality Assurance Business" as it's a topic that's close to our hearts at the moment, as we're going to be debating about whether we are QA or Test in a Community event tomorrow, so that should be interesting! (I'm advocating for Test Engineers obviously!) It's important to choose a blog post that the people reading it will get something out of, and not just read it and think "WTF did I just read!?" I think this blog post offers value to both Testers and Non Testers and will hopefully help them understand what we do!

Whilst it's not great that I didn't manage to do any over the weekend, I did manage to do some reading of my Testing Book (Dear Evil Tester), so that's something... The book itself is interesting and I quite enjoy the humourous writing style, though I'm going to finish it soon, so I may end up getting another one, I'm looking at Explore It! as a number of other people are reading it also!


  1. Nice article... unfortunately the picture of the QA++ session isn't showing... not sure if this counts as #5 Read and comment on a blog post, or #13 Find a user experience bug!

  2. Much better. Now who is that handsome chap at the top of the picture?!


Post a Comment

Popular posts from this blog

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…

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.

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

        private s…