Cool stuff! Do you have any information on writing tests against asynchronous APIs?
I've made heavy use of jquery events for testing asynchronous calls with ScrewUnit, but I don't see anything here to cover that. I guess if jquery loads you could just use that on top of this.
Speaking of ScrewUnit, if you came up with a version of this that ran a BDD framework like Jasmine or ScrewUnit I'd be sold.
Something I really want from a JS testing framework is browser independence. I don't mean running in any browser; I mean ability to run *without* a browser, for example under a Rhino console.
I think a unit test engine should have its UI cleanly separated just like JUnit is. Backend providing asserts and not using anything that isn't in the ECMA standard, and frontend providing a UI.
Which could be an HTML UI relying on a browser DOM, a command line UI relying on Rhino, a runner that silently sends results using XMLHttpRequest, or a Yahoo Widget frontend.
Hey ehud, we (I work with Misko) have a new test runner called Testacular. And yep, it does work on Windows. You can check it out on https://github.com/vojtajina/testacular
It is a very nice implementation of a great idea. Thanks for sharing!
ReplyDeleteCool stuff! Do you have any information on writing tests against asynchronous APIs?
ReplyDeleteI've made heavy use of jquery events for testing asynchronous calls with ScrewUnit, but I don't see anything here to cover that. I guess if jquery loads you could just use that on top of this.
Speaking of ScrewUnit, if you came up with a version of this that ran a BDD framework like Jasmine or ScrewUnit I'd be sold.
Nice work and thanks!
Something I really want from a JS testing framework is browser independence. I don't mean running in any browser; I mean ability to run *without* a browser, for example under a Rhino console.
ReplyDelete@Nicolas checked out Blue Ridge? The project itself is rails-centric but the concepts should be applicable to other projects without too much effort.
ReplyDeleteNicolas, you could also check the aptly named rhinounit, which runs inside rhino and can be triggered via Ant.
ReplyDelete@Nicolas: there is also CrossCheck:
ReplyDeletehttp://thefrontside.net/crosscheck
I think a unit test engine should have its UI cleanly separated just like JUnit is. Backend providing asserts and not using anything that isn't in the ECMA standard, and frontend providing a UI.
ReplyDeleteWhich could be an HTML UI relying on a browser DOM, a command line UI relying on Rhino, a runner that silently sends results using XMLHttpRequest, or a Yahoo Widget frontend.
I'm very impressed with the tight feedback loop this provides!!!
ReplyDeleteMisko, is there a way to use this in win 7?
ReplyDeleteThanks
Hey ehud, we (I work with Misko) have a new test runner called Testacular. And yep, it does work on Windows. You can check it out on https://github.com/vojtajina/testacular
ReplyDeleteThanks
ReplyDelete