So the basic problem is that when you load the instantiate page there is
an ajax call to the profile info. Normally this returns before the user
has a chance to move the mouse the Next button. When there are 40 or so
loads of that profile, its take longer and the test harness 'clicks'
next before its ready for it. The steps package we use does not have a
concept of disabling the next button until some event is ready, so I
have to add that. Turns out the same exact problem happens on Step two;
the parameterize step is not ready before the harness clicks the next
button again. The test harness can look/wait for a button to become
enabled, but only if something disables the button. Every one of the
errors is some form of this problem. Anyway, users will see the same
exact problem on a super loaded boss; they will click next and the page
will break during the tutorial.

Later ... turned out to be easy to disable the buttons, but they are
links and Selenium does not have a way to deal with a disabled link.
So I am doing this by changing the class of the buttons to look
disabled, removing the click event handler, and adding a hidden div
element that we can look for.

Lets see if this works.