Learn how to write acceptance tests and test "user stories" with your applications using the new doh.robot module, dijit.robotx, for Dojo 1.2, without modifying your application code or even upgrading your version of Dojo.

We are using doh.robot api to perform UI testing for our application.We came across following issues

1) When dojox.robot.recorder was used to record the events performed on my application which is available inside the iframe of the runner.html, the recorder was not able to identify the elements in my application using their dom ids(for eg: mouseMoveAt funtion).

Moreover i would like to have the test files separated from the application.

please throw us some light in this context as we are new to doh.

Last week I added an unprecedented enhancement to the Dojo Object Harness (DOH) unit test framework, called doh.robot, scheduled to appear in Dojo 1.2. This enhancement adds an API to DOH that enables testers to automate their UI tests using real, cross-platform, system-level input events. In this post, I'm going to explain the enormous value-add of this enhancement in terms of unit and accessibility testing, and how to get started using this new API.

I have some suggestion about DOH. Overall I think its a great tool, and I think its asynchronous testing support is fabulous. But honestly, I just don't find it that intuitive to get up and running quickly, and I think some simple changes could fix that.

1. Lets make doh a first class package. Pull it out of util and make it just as important as dojox and dijit. Don't you think it is? And by not burying it, I think we could encourage its use.

2. Runner.html: Having the DOH Runner default to running all the tests in dojo is distracting. How about getting rid of:

Does DOH support cross domain?

I got error when I tried to run DOH testing in cross domain. "doh is not defined"

Thanks

Wendy