Browser test suite

[kriskowal]

Browser test suite

[domenic]

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.

[Gozala]

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.

[domenic]

@Gozala That sounds excellent, since I think our goal is just to check that we didn't break anything.

[Gozala]

@domenic Ok I'll try to do it over the weekend & maybe provide a patch for q that would do that!

[kriskowal]

I’ve got a pull request open for promise support in Jasmine.

jasmine/jasmine#202

[domenic]

I think the best stack right now would be BusterJS for native "return a then-able" support + Chai + Chai as Promised. I haven't used BusterJS yet but the latter two are working great in our project at work.

[kriskowal]

Ok. If Buster doesn’t work out, we can use Jasmine instead. It’s relatively straightforward to monkey-patch jasmine.Block.execute.

[kriskowal]

Landed in v0.8.5