blanket qunit ? about blanket HOT 5 CLOSED

Yes, I did make the build script change the name. Basically you wouldn't
use a qunit plugin with jasmine tests. You wouldn't expect it to be
seamless. So my thought was why would this be any different. People will
only need one version of the script.

I agree with it not being seamless otherwise, but it is a really heavy
library right now, so I think that for the moment we should separate it out
and then after we've resolved other issues we bring it together. It
wouldn't be a problem doing it that way because the test part and reporter
part are included in the build script, so we'd just need to wrap those
parts in an if block:

if (typeof QUnit !== "undefined"){ //use /lib/qunit.js }else...

On Mon, Oct 29, 2012 at 3:27 AM, Pierre [email protected] wrote:

Do you plan to distribute 3 versions of Blanket ? I saw you name it
blanket_qunit.js ?

I think, if we really want to be seamless we will need to have the 3
working on the same files. I know it will be heavy and that it would maybe
add some "hacky" code but we will keep a freaking easy configuration :)

Maybe you just did that for test purpose ?

—
Reply to this email directly or view it on GitHubhttps://github.com/Migrii/blanket/issues/45.

from blanket.

ok. So, one script by library for now (the builder will do the stuff for us) and will see later if we combine them or not :)

from blanket.

Yep.

I think that would help if anyone started using it too because we can tell
them the qunit build works but that the others don't.

On Mon, Oct 29, 2012 at 7:55 AM, Pierre [email protected] wrote:

ok. So, one script by library for now (the builder will do the stuff for
us) and will see later if we combine them or not :)

—
Reply to this email directly or view it on GitHubhttps://github.com/Migrii/blanket/issues/45#issuecomment-9863732.

from blanket.

I think long term we'll offer several downloads.

1. Everything. A file that works in browser and server and includes all test runners.
2. Client version specific to the test runner
3. Published package in npm

Additionally, we'll document the build script and make it so people can build their own and maybe mixin custom test runner code, or expose an API so they can tie in their own test runner code.

from blanket.

So I think the plan would be to have the npm version for server, and one browser for in-browser. For now only qunit is supported but when we get jasmine working we'll just change the builder and whatnot and then make an api for other test runners and let people add them in as plugins.

from blanket.