New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mechanism to dispatch native browser events #73
Comments
Any suggestions on how that should work? Are you looking for something like simulate.js? |
Yep, pretty much something exactly like that. (UI always seems to be one step ahead. :)) I think that this would have application for pretty much anyone writing interactivity tests using QUnit, not just jQuery. |
Marc ripped simulate.js apart a bit: http://marcgrabanski.com/articles/simulating-mouse-click-events-in-javascript |
Scott says we should port the DOH Robot instead: http://dojotoolkit.org/reference-guide/util/dohrobot.html |
Josh's keymasher plugin: https://github.com/digitalBush/jquery.keymasher |
I'm a big fan of FuncUnit. And is largely based on QUnit. |
Ephox also implemented the a similar thing with https://github.com/ephox/JSRobot/. Having used it, I doubt if the API is as strong as dohrobot. If you want native events you're pretty much going to have to go with a solution that uses a java applet to create those native events. Simulate comes close, but it'll never actually measure up 100%. |
Making this a documentation ticket. There are various options, where both JSRobot and syn look the most interesting. QUnit docs should reference those, beyond that I don't see anything we can really do here, its out of scope. |
Fixed in qunitjs/qunitjs.com@a0b63ba, live at http://qunitjs.com/cookbook/#testing_user_actions |
It would be nice if QUnit had a mechanism that would allow for easy dispatching of native browser events on elements instead of needing to reinvent the wheel for every test suite that needs to test events. Right now, for instance, the vast majority of jQuery unit tests are only testing the jQuery event system and don’t actually ever confirm that native browser events will work the same way.
The text was updated successfully, but these errors were encountered: