-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
higher level js api #265
Comments
I have a jQuery plugin that runs its unit tests against each supported version of jQuery in a loop. I would love to replace my home-grown testrunner with mocha. Any idea how big the scope of enabling an API is? Hacking _mocha to import each version of jQuery is proving difficult. I'm sure require('mocha') with supported functions would work much better for my case. |
wouldnt you want to run that the browser anyway |
I'm running a subset of the unit tests in jsdom continuously during development. Then manually running the full suite in browsers before a release. |
ah I see. well can't you just have require('jquery1.0') require('jquery1.1') that sort of thing? |
then maybe setup the makefile like:
|
^ gives you the benefit of concurrency as well |
Interesting. I'll give this a shot since I need a makefile's easy access to my scripts anyway. Thanks! Mind you, this is part of a larger build system that does things like JSHint for syntax, compile Stylus and minify the source before running the tests. That's why having the whole thing written inside a Node.js module, using an API provided by mocha makes the most sense to me. |
sure, but at least until there is a js api |
Agreed, and P.S. - I <3 the flexibility of this test framework. It's the least opinionated one by far. |
would allow people to bypass mocha(1) if they wish, see #136 and a few others
The text was updated successfully, but these errors were encountered: