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!

Labels:

Comments

  1. Unknown12 July 2016 at 02:33

    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!

    ReplyDelete
  2. Unknown12 July 2016 at 04:42

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

    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