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. research paper service12 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

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