Skip to main content

Happy Cake Day to me!

It's about a year since I started writing blogs, so thought it would be nice to look back and say how blogging has improved me.

Firstly, there have been numerous times when I've thought I wrote a blog post about that, let me dig it out, and use it as my own reference or even for someone else, so it has definitely made things like that easier.

It has also made me more knowledgeable about topics that I have written about, if I'm going to write a blog post about something I want to be sure that:
  • I know what I am talking about
  • It's all correct
  • It's articulated in a way that people will understand
That's lead to me researching things more, and actually delving outside of my comfort zone a little bit.

Then there's reading other peoples blogs to ensure that I'm not just copying what others have written, so becoming more knowledgeable that way, reading other blogs also helps give me ideas about what to write about and ensures that I don't run out of ideas :p

There's also the coding type of blogs that I've written, which I've often looked back on and used as reference for future work. Hopefully others have found them interesting and useful.

I thought I'd put my 3 favourite blogs that I've written over the past year here as well, almost like a highlight reel :)

So in nor particular order:
  • Mindset of a Tester -I had a lot of fun writing this blog post, it's about football and testing, so it was nice to think outside of the box a little bit and apply something to do with a hobby to my job.
  • Performance Testing 101 - I often find myself coming back to this post more than others, just to refresh my brain on the different types of performance testing, so it has definitely come in useful. It's also got the most number of page views of any blog post that I've done.
  • Testing and American Football - A comparison - This was probably the most fun blog post to write, and it's just meant as a bit of fun to read, so don't take it too seriously!
It's definitely been a fun journey, and the above really are only a selection of the highlights that I've written about over the year!

May the next year bring as much fun and interesting posts as the previous!



Labels:

Comments

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