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!?


Comments

  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

    ReplyDelete
  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

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

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

The Stickman Tester... The full version complete with deleted "scenes"!

As some of you may have seen, a little while ago I performed a 99 second talk on the Stickman Tester for the Ministry of Testing. Owing to the fact that it had to be 99 seconds, this unfortunately meant that a verse was left out in order to keep it within the time frame! It's only now that I have found the time to put the deleted verse/scene back in, and re-record it and upload it! (It's now a 120 second talk!) It talks about a testers journey in an Agile team, about how not everybody has it as good as others, and basically talks about not giving up, keep searching, or trying to change your role to make it what you want it to be. Anyway, here it is, in all it's glory. Hope you enjoy it!