Skip to main content

Using bugs to your advantage....

Over Christmas I had the pleasure of taking my son to see Santa Claus, however unfortunately it gets rather busy if you don't prebook online, we decided in the morning on a Saturday, that we'd take him to see Santa that afternoon, so decided to look online to book to avoid the queues.

So I logged on, and went to book online, however unfortunately it would only allow you to book for the next day and you couldn't book for the same day, as it wasn't selectable in the drop-down. 

Luckily for me, I selected tomorrow and went to confirm in case we decided to go tomorrow, I happened to have a look at the URL that it generated, sure enough the date was in the URL, so I changed the date in the URL to today and it managed to take me to a confirmation page with a confirmation number confirming my appointment for today! :) Finley will be pleased, and so would mummy and daddy at not having to wait in the queue.

So we got to Santas Grotto, and sure enough the queue was massive, my wife was still sceptical that it would work, but I assured her that it would be fine, however unfortunately I realised why they didn't let you book for the same day, they must print out the online bookings first thing in the morning, there was no record of our booking in their printout, but I showed them the confirmation, and after some puzzled looks they let us through :)

Looking back now, I should have let them know (after I went of course) that I'd found a bug in their system, which whilst small, and not really affecting their users, it did allow me to jump the queue, I don't feel bad about it though, as Finley was extremely happy to see Santa, though he wasn't sure about him at first! 

I guess the moral of this story, is that a testers brain never changes, always looking for ways to break the system, even when not at work! Sometimes though, this can be to your advantage... :)


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.

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

        private s…

Famous Movie Quotes applied to Software Engineering - Jaws

You're gonna need a bigger boat? How can that relate to Engineering?

Firstly, let me ashamedly admit, that I've never seen the whole of Jaws all the way through. It's on my list of films to watch, but whether I get round to it, is another matter!

Anyway, to apply this to engineering, it's almost like "you're gonna need more testers/developers"...

We hear this all too often when trying to push releases out the door, let's throw men at it... However, as we all know, a bigger boat/more men... isn't always the answer, it's not a guarantee of quality, or even a guarantee of getting things done quicker.

If you have a task that will take 2 hours, simply having 2 people work on it doesn't mean that it is halved, in fact often, the time taken to do the task remains at 2 hours, but the maintainability and the knowledge around that area is increased, so it's a price, in my opinion that is often worth paying.