You're probably better off using dojo/domReady! rather than dojo/ready.
Probably the simplest approach is to have something within your block of
code that specifies either a global or something inside the dojo/config
block that you can poll against to see if it has been set. The advantage
of this is that you've explicitly stated that your application has
finished reaching the state you prefer before testing commences.
on 3/14/17, 15:49 (GMT-07:00) Mikhail Ramendik said the following:
> Asked once but probably formulated it wrong...
> I know that one can use dojo/ready register an event to run when the
> page is fully ready.
> differnt value based on whether the dojo/ready state has been
> I would use this for WebDriver testing.