Usage question

[voidpp]

I tried to use this stuff, but I failed.
In debian wheezy I installed the nodejs (v0.10.28), from the source, configure, make, make install, everything goes wonderful.
After I installed the qunit-cli by "npm install qunit-cli -g", and it still looked fine. (qunitjs@1.10.0)
Here is my very complex test

if (typeof QUnit == 'undefined') // if your tests also run in the browser...
    QUnit = require('qunit-cli');

// use QUnit as you normally would.

//module( "group a");

test("hello test", function() {
        ok( 1 == "1", "Passed!" );
});

If I try to running this by "qunit-cli mytests.js" the result is:

/usr/local/lib/node_modules/qunit-cli/index.js:44
            console.log('\n' + details.module.bold.blue);
                                             ^
TypeError: Cannot read property 'bold' of undefined
    at F.QUnit.done.msg (/usr/local/lib/node_modules/qunit-cli/index.js:44:46)
    at runLoggingCallbacks (/usr/local/lib/node_modules/qunit-cli/node_modules/qunitjs/qunit/qunit.js:1382:19)
    at Object.Test.finish (/usr/local/lib/node_modules/qunit-cli/node_modules/qunitjs/qunit/qunit.js:253:3)
    at /usr/local/lib/node_modules/qunit-cli/node_modules/qunitjs/qunit/qunit.js:285:10
    at process (/usr/local/lib/node_modules/qunit-cli/node_modules/qunitjs/qunit/qunit.js:1277:24)
    at null._onTimeout (/usr/local/lib/node_modules/qunit-cli/node_modules/qunitjs/qunit/qunit.js:383:5)
    at Timer.listOnTimeout [as ontimeout] (timers.js:110:15)

because the "details.module" is undefined. Then I try to define a module with the module function as the qunit doc writes, but the result is:

/home/santa/devel/tests/mytests.js:6
module( "group a");
^
TypeError: object is not a function
    at Object.<anonymous> (/home/santa/devel/tests/mytests.js:6:1)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at /usr/local/lib/node_modules/qunit-cli/bin/qunit-cli:57:3
    at Array.forEach (native)
    at Object.<anonymous> (/usr/local/lib/node_modules/qunit-cli/bin/qunit-cli:56:7)

I tried to look for solution for this problem, but not found anything, and I don't know what is the problem...

[piranna]

Seems it's related with the colors dependency instead of qunit-cli itself, or maybe the qunitjspackage, could you tell us what versions got installed?

[voidpp]

The whole result of the "npm install qunit-cli -g" command:

npm http GET https://registry.npmjs.org/optimist
npm http GET https://registry.npmjs.org/qunitjs
npm http GET https://registry.npmjs.org/colors
npm http 304 https://registry.npmjs.org/optimist
npm http 304 https://registry.npmjs.org/qunitjs
npm http 304 https://registry.npmjs.org/colors
npm http GET https://registry.npmjs.org/wordwrap
npm http GET https://registry.npmjs.org/minimist
npm http 304 https://registry.npmjs.org/wordwrap
npm http 304 https://registry.npmjs.org/minimist
/usr/local/bin/qunit-cli -> /usr/local/lib/node_modules/qunit-cli/bin/qunit-cli
qunit-cli@0.1.4 /usr/local/lib/node_modules/qunit-cli
├── colors@0.6.2
├── qunitjs@1.10.0
└── optimist@0.6.1 (wordwrap@0.0.2, minimist@0.0.8)

[piranna]

Wait...

//module( "group a");

Why is that commented? Would this be the reason? details.module is undefined, but if there's no current module, it makes sense... Please uncomment it and check again, if it works, then we should see if it's a bug on qunitjs by not providing a default module name (that it's logical) or a bug of qunit-cli by not considering undefined QUnit modules.

[piranna]

http://api.qunitjs.com/QUnit.testDone/

1 🍺 for everybody if this is not the source of the problem ;-)

[voidpp]

Unfortunately this is not the source of the problem :)
As I wrote: "Then I try to define a module with the module function as the qunit doc writes, but the result is: ....".
If I uncomment the specified line, the "TypeError: object is not a function" error is appearing.

[piranna]

QUnit-cli doesn't export globals as it's browser counter-part does, so you need to call it with the full namespace (QUnit.module()). If you want to use the test the same as in the browser, the test-runner located at bin folder does that :-)

I'll fight until dead to don't need to pay your 🍺... ;-)

[voidpp]

Yey, it's working! Thanx for the help.

But I have to mention that in this case the readme needs some update.
"// use QUnit as you normally would." I think this not true in this example, because the module function only usable with the QUnit namespace...

But the other hand, there is a bug in the qunit-cli, about the undefined QUnit modules...

[piranna]

Yey, it's working! Thanx for the help.

Yo own me a 🍺 ;-)

But I have to mention that in this case the readme needs some update.

"// use QUnit as you normally would." I think this not true in this
example, because the module function only usable with the QUnit namespace...

It's explained just on the next line, but it wouldn't hurt to make it more
explicit...

But the other hand, there is a bug in the qunit-cli, about the undefined

QUnit modules...

You are right. Luckily this is an easy one... :-)

[voidpp]

It's explained just on the next line, but it wouldn't hurt to make it more explicit...

Ok, this is true, but I really like example codes... :)