search

rsjudge17 / ubiquity-xforms

Automatically exported from code.google.com/p/ubiquity-xforms
0 stars 0 forks source link

Some automated test driver pages use waitForModelReady incorrectly #577

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
I've just noticed that there are using waitForModelReady in the driver page, 
even though the test is actually supposed to fail with a fatal exception 
during initialisation.

These references to waitForModelReady should be removed from those driver 
files, so that the tests can pass.

The ones that I spotted were in chapters 3 and 4 of the test suite, but there 
may be others.

Original issue reported on code.google.com by phil.boo...@gtempaccount.com on 2 Oct 2009 at 2:50

GoogleCodeExporter commented 9 years ago 
There are a couple scripts that do use the waitForModel ready. This seems to be 
an
issue that needs a special driver written in Selenium. one of the issues with 
this is
that we need to access the XForms processing engine properties directly to 
check for
dispatched events etc if we are going to wait for a dispatched event.

Original comment by erik...@gmail.com on 7 Oct 2009 at 9:21