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!



Comments

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

[AfterTestRun]
        public static void AfterTestRun()
        {
            var nativeDriverQuit = Task.Factory.StartNew(() => Driver.Quit());
            if (!nativeDriverQuit.Wait(TimeSpan.FromSeconds(10)))
            {
                CleanUpProcessByInheritance();
            }
       }

        private s…

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…