Skip to main content

A Tester goes to Disneyland!

A few weeks ago I went to DisneyLand Paris with the family, and it's the first time I've been to a theme park and really took advantage of the Fast Pass system they have! I have to say it's really great! Especially with kids!

For those that don't know the fast pass enables you to "book" a time to come back to a ride and go on it, it's invaluable with kids especially as it meant we'd spend less time queueing, and as good as my kids are at queueing (we are British after all!) it's not the best way to spend a holiday! Luckily for us it wasn't too busy and the longest time we queued was probably around 30 minutes.

It got me thinking and wondering how it went, which is generally a Testers mindset, asking How is this even possible? Why is this happening? How does it work?

Anyway, I did a bit of googling, and sure enough someone else had asked on Stack Overflow of all places how it works, and it's a way of scheduling rides for people, and ensuring that rides aren't being unused elsewhere. From Disney's perspective ensuring that people aren't standing around in queues is great, as it means they'll be spending money potentially or even just getting more rides in and having more fun! A happy theme park is a good theme park!

The link to StackOverflow is here...

We do this in testing/engineering as well, especially with regards to automation and running CI builds! We schedule our CI Builds generally to run at a quiet time, so as to not interrupt with anything else that might be happening. Or even in just scheduling when we can test something or deploy something, ideally we want to test things first in isolation so as to isolate if anything is broke then we know the reason.

Or if we are waiting to test something, and we know we have something already in test, then it makes logical sense to spend our time testing that and not sitting around doing nothing whilst we wait for the other thing to test!





Comments

  1. Anonymous12 October 2017 at 09:18

    Great Blog! If you are not sure or confident about anything than ask questions and clear your doubts about that particular matter.

    ReplyDelete
  2. WintyWen17 April 2019 at 04:45

    Great post. I was checking constantly this blog and I am impressed! Very helpful info particularly the last part :) I care for such info a lot. I was seeking this particular info for a very long time. Thank you and best of luck. professional web design

    ReplyDelete
  3. RafaelKlimek22 April 2019 at 19:05

    whoah this blog is great i love reading your posts. Keep up the good work! You know, many people are hunting around for this information, you could aid them greatly. a math tuition singapore

    ReplyDelete

Post a Comment

Popular posts from this blog

Delusions of Testing

So I've got in touch with my old QA friend, Richard Lee and we spoke about guest blogging on each others blogs... Richard is an IT Professional for a FinTech based company in London. His activities vary from Release Manager, Build Manager, Database Administrator. Working in a Microsoft workshop, his expertise lies in MSBuild/Workflow/Powershell/SSAS/SSIS/SSRS/SQL, basically whatever isn’t anyone elses’ problem is Richard's problem! When not solving other peoples problems he can be found blogging at redphoenix.me , and jogging to and from home, where he lives with his heavily pregnant wife. Hello, my name is Richard, and I am a former tester. Like most people and their careers, I fell into testing; I first got into testing about 6 years ago, after I had graduated. I went to a university where the attitude was that you should try to get on a graduate scheme with one of the big companies. If you weren’t interested in that, well, good luck with getting any support from ...
3 comments
Read more

QA is Awesome!

No real point to this post other than I have had the song stuck in my head and figured I could change it slightly and quite easily make QA is Awesome! Oh and I haven't even seen the movie all the way through! But for some reason that song is incredibly catchy! Not much point to this post in fact, just thought I'd put it out there :)
Post a Comment
Read more

Treating Test Code as Production Code

It's important when writing automated tests to remember that the code you write should be up to production standards, meaning any conventions that you have in place should be adhered to and that it should follow good design patterns. Too many people often say why does it have to be as good as production code, it's "Only" a test, so long as it passes then that's fine... To answer this we need to look at why we want our tests to be written in such a structured and efficient manner: - Maintainability - by making the test code structured and efficient, it becomes far easier to maintain and in doing so changes in the future can happen quickly as the test isn't linked to anything that it shouldn't be and it's easy to understand for a new set of eyes. - Durability - Again by making the tests structured they should be resistant to changes, if you change a variable name for instance then it shouldn't effect the unit test unless it absolutely has to....
1 comment
Read more