Actually, once I got the syntax down, doing the integration with Syn worked great. It functioned like a MUCH faster selenium for me.
I've been trying to get the messing with trying to get the mootools-test-runner working (haven't tried *too* hard really though), and Syn seems like a much cleaner, same language solution to me. I think there will always be benefits to being turtles all the way down, you just have to deal with the quirks of the language that your working in. On Fri, Oct 22, 2010 at 1:06 AM, Thomas Aylott <[email protected]>wrote: > Simple. You wouldn't. > Testing JavaScript using JavaScript is like letting bank robbers police > each other. > > Seriously though, there is a decent tool for doing this in the Dojo > universe. My hackathon project for next Thursday will be to make the Dojo > doh.robot run using our testing system. > > Longterm I plan on collaborating with Dojo and many more to standardize or > conventionalize automated UI testing. > > — Thomas Aylott / SubtleGradient.com (from iPhone 4) > > On Oct 19, 2010, at 2:57 PM, Greg Moeck <[email protected]> wrote: > > > I'm trying to write some integration/acceptance tests for an > > application that I'm writing that uses Sortables, but I'm having some > > trouble simulating the dragging. My plan was merely fire the events > > for mousedown, movemouse, and and mouseup, but when I use > > element.fireEvent, the Sortables start method fails, since a true > > event is not passed in. I'm pretty sure it's just my lack of > > understanding of javascript, but how would you go about doing > > something like this? >
