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. Dharani M29 November 2018 at 22:36

    Nice blog. thank you for sharing this information
    DOT NET training in Marathahalli

    dot net training institute in Marathahalli

    dot net course in Marathahalli

    best dot net training institute in Marathahalli

    ReplyDelete
  2. Dharani M11 December 2018 at 03:35

    Really nice blog
    digital marketing courses in Marathahalli with placement

    digital marketing training in Marathahalli

    seo training in Marathahalli

    ReplyDelete
  3. JeanScott25 December 2018 at 07:28

    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
  4. REBBCADAVids10 February 2019 at 02:44

    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

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