Skip to main content

#GarethSouthgateWould as a Software Tester

Gareth Southgate has impressed me massively over the past few weeks. The empathy and compassion he has shown to other players, the way he has made this tournament about the team and not about any individual is amazing.

I was reading the #GarethSouthgateWould hashtags on Twitter and there were some classics in there. I'll let you read them for yourselves, but I thought it would be cool to make it themed towards testing, here are some I came up with off the top of my head... Though I am sure there are more.

#GarethSouthgateWould - Ensure that automated checks clean up after themselves

#GarethSouthgateWould - Share with other testers blogs and articles they have read that they enjoyed

#GarethSouthgateWould - go through and remove any Thread.Sleeps from any automated checks

#GarethSouthgateWould - Take time out to help another tester who is struggling with something, even when he doesn't know the solution.

It made me realise that these are all things that a caring and compassionate good tester should do anyway, these are things that I like to think I would do anyway.

What else would Gareth Southgate the software tester do!?


  1. Howdy! I could have sworn I've been to this website before but after reading through some of the post I realized it's new to me. Anyways, I'm definitely happy I found it and I'll be book-marking and checking back frequently! social media marketing proposal

  2. I would repeat that we website visitors actually are unequivocally lucky to dwell in a great network with so many special professionals with interesting principles. I feel quite privileged to have come across the site and look forward to plenty of more awesome moments reading here. Thank you again for all the details.industrial control systems


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…