Test runner based on Tape and Browserify

Right now I'm seeing this error when running my test suite. I suspect one of my test files is throwing an error, but Prova doesn't show me any useful information. What can we do about this?

https://cloudup.com/cjJhMEU817G

Looks like there's a missing dep?

prova:browser Failed to browserify the source code. We're probably missing a module required. The error was: +15s

    Cannot find module 'sha.js' from '/…/node_modules/prova/node_modules/browserify/node_modules/crypto-browserify' /…/node_modules/prova/node_modules/browserify/node_modules/resolve/lib/async.js
                        v
    49.         else if (core[x]) return cb(null, x);
    50.         else cb(new Error("Cannot find module '" + x + "' from '" + y + "'"))
    51.     });
                        ^
    Error: Cannot find module 'sha.js' from '/…/node_modules/prova/node_modules/browserify/node_modules/crypto-browserify'

I've not been able to isolate this to a reproducible scenario, but it seems to happen when async tests fail to end(). I also seem to encounter some false plan != count errors, not sure if that is related.

I will continue trying to isolate, but I figured I would report in case you have ideas on what could be the issue. Screen grab of console: http://cl.ly/image/2a392W0I3c3M

run.js is never returning. The read.bundle({ debug: true }).pipe(write); call in lib/browser.js appears to be failing, but I haven't figured out why. Any ideas?

I am running into this on a fresh install of prova.

This transform will replace all instances of "tap" or "tape" require statements in a script with require('prova'). This closes #2.

The first commit updates all out of date dependencies except for Browserify and Watchify which both require a rewrite in order to support the latest versions.

The second commit updates both browserify and watchify.

Both have changed quite a bit since the versions tracked in the current iteration of Prova. This required a bit of an overhaul to the current way that prova interfaces with the two. Specifically it was neccessary to modify lib/browser.js and lib/browserify-transform.js to support the latest api.

This would be nice to have in order to

• test stuff like ajax calls, image loading etc.
• misuse prova as a rapid prototyping server (like beefy). I have been doing that :)

(pull request is coming up)

One of the advantages of TAP is that it produces output in a simple, standard format that can be piped into other tools, e.g. faucet. It would be nice if prova-the-library preserved this property, and produced TAP-compliant output when run via node test.js. It's fine if prova-the-command, e.g. prova test.js produces a custom output format.

When browserify.bundle() emits an error, the error object seems to be improperly transformed for display in console output. It looks like prova is expecting error to be a string when it's actually an Error object. I am using prova with browserify 4.1.11.

The console output reads like the following:

prova:browser Failed to browserify the source code. We're probably missing a module required. The error was: +261ms

    undefined

In my tests, the error itself is an Error object, and looks like this:

{
   "message": "reserved word \"var\"",
   "line": 1,
   "column": 1,
   "annotated": "/Users/ahutchings/Projects/myproject/test/test-file.coffee:1\nvar TestClass, test;\n^\nParseError: reserved word \"var\""
}

When I run:

git clone https://github.com/azer/prova.git
cd prova
npm install
npm test

I get this output:

> [email protected] test /Users/jchris/code/js/prova
> node test.js


module.js:340
    throw err;
          ^
Error: Cannot find module '/Users/jchris/code/js/prova/test.js'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Function.Module.runMain (module.js:497:10)
    at startup (node.js:119:16)
    at node.js:906:3
npm ERR! Test failed.  See above for more details.
npm ERR! not ok code 0

When I run prova from inside my working directory, I get:

    assert object
    should be equal /Users/jchris/code/js/prova/test/index.js
                    v
        4.   assert.plan(4);
        5.   assert.equal(3.15, 3.14);
        6.   assert.ok(true);
                    ^
        Error: should be equal
            at Test.assert (/Users/jchris/code/js/prova/node_modules/tape/lib/test.js:188:54)
            at Test.bound [as _assert] (/Users/jchris/code/js/prova/node_modules/tape/lib/test.js:59:32)
            at Test.equal.Test.equals.Test.isEqual.Test.is.Test.strictEqual.Test.strictEquals (/Users/jchris/code/js/prova/node_modules/tape/lib/test.js:311:10)
            at Test.bound (/Users/jchris/code/js/prova/node_modules/tape/lib/test.js:59:32)
            at Test.<anonymous> (/Users/jchris/code/js/prova/test/index.js:5:10)
            at Test.bound [as _cb] (/Users/jchris/code/js/prova/node_modules/tape/lib/test.js:59:32)
            at Test.run (/Users/jchris/code/js/prova/node_modules/tape/lib/test.js:72:10)
            at Test.bound [as run] (/Users/jchris/code/js/prova/node_modules/tape/lib/test.js:59:32)
            at Object.next [as _onImmediate] (/Users/jchris/code/js/prova/node_modules/tape/lib/results.js:66:15)
            at processImmediate [as _immediateCallback] (timers.js:336:15)


        Expected: 3.14
        Actual:   3.15




    1 failed, 3 passed assertions.

Which doesn't seem like it's running all the tests in test/

And when I run prova -b I get a browser window with that same output (only the one failing test).

Is this the expected behavior? I'd like to be using prova heavily on a project but without a test suite, I don't know where to start on fixing little bugs I find with it.

Thanks for any pointers!

Hello, I have been happily using prova and loving it.

How do you run multiple test files with prova ?

It seems tape *.js will do it but I think prova would benefit in having a prova bin.

What do you think?

I update package dependencies to latest and all 7 test passed.

Is a warnnig on the command line:

npm WARN [email protected] license should be a valid SPDX license expression

that can be solved is you choose another, more specific, BSD license

If we run test in browser and throw exception:

var test = require('prova');

test('smth', function(t) {
    throw new Error();
    t.end();
});

Test case does not end and error appears only in browser console, but not in command line.

Enable instantiating Browserify from args.

If --browserify command is passed, it will proxy instantiation of Browserify and ignore automatic prova extensions, transforms and plugins.

This request constitutes a 'feature' version bump in package.json.

README.md has also been updated to document the change.

Browserify currently breaks because files contains the cli ('/bin/prova') and then the files it should be browserify*ing. This fixes that

Currently browserify will error immediately!

See https://github.com/azer/prova/pull/62 first /cc @azer

test.js:

var test = require('prova');

test('a', function(t) {
    t.test('b', function(t) {
        t.equal(2 + 2, 4);
        t.end();
    });
});

I expect -g b to run this test, but:

$ prova test.js 

    1 passed assertions.

$ prova test.js -g b

    0 passed assertions.