-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Browser test suite #54
Comments
On first thought the best route is to use something like lobrow to get dirt-simple Node-modules-in-the-browser up and running. I also think @substack had a recent one but I can't find it in his monster list of public repositories. @Gozala/test-commonjs seems like it would work pretty well in such an environment, since it doesn't depend on much environment, and is already browser-compatible in at least some fashion (AMD might be involved?). Another option would be to have a compile step for the tests that wraps them in and AMD wrapper to be used alongside @Gozala/test-commonjs. I believe @jrburke/r.js can do this. |
In fact I have version of test-commonjs somewhere that can run tests in browser, using some AMD like module loader. It's far from being pretty but it runs tests and logs results to the screen. I could share it with you if that helps, but I'm not able to put much effort in making it first-class for now. |
@Gozala That sounds excellent, since I think our goal is just to check that we didn't break anything. |
@domenic Ok I'll try to do it over the weekend & maybe provide a patch for q that would do that! |
I’ve got a pull request open for promise support in Jasmine. |
I think the best stack right now would be BusterJS for native " |
Ok. If Buster doesn’t work out, we can use Jasmine instead. It’s relatively straightforward to monkey-patch jasmine.Block.execute. |
Landed in v0.8.5 |
We need a way to run tests in browsers to validate the releases. @Gozala’s CommonJS unit test suite work great in Node.
We must have a solution that works for both browsers and Node. I would accept a temporary solution that ports the tests to Jasmine or something. I would accept a solution that embeds a mini module loader to run the tests client-side.
The text was updated successfully, but these errors were encountered: