Closed jchris closed 9 years ago
looks like I accidentally committed that line failing 3.14 != 3.15
Now when I run the above sequence ending in npm test
I get the following result. I would love to contribute to prova (I especially want to be able to use it as part of a gulp toolchain, but I imagine the path to get there will touch on lots of little things.)
I don't feel comfortable cracking open the source code until I know I won't break existing behavior.
$ npm test
> prova@1.15.0 test /Users/jchris/tmp/prova
> prova test/*
module.js:340
throw err;
^
Error: Cannot find module '/Users/jchris/tmp/prova/test/altjs'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at /opt/boxen/nodenv/versions/v0.10.28/lib/node_modules/prova/lib/cli.js:60:5
at Array.forEach (native)
at node (/opt/boxen/nodenv/versions/v0.10.28/lib/node_modules/prova/lib/cli.js:59:9)
at /opt/boxen/nodenv/versions/v0.10.28/lib/node_modules/prova/lib/cli.js:43:39
at /opt/boxen/nodenv/versions/v0.10.28/lib/node_modules/prova/node_modules/flat-glob/index.js:15:7
at next (/opt/boxen/nodenv/versions/v0.10.28/lib/node_modules/prova/node_modules/flat-glob/node_modules/iter/lib/serial.js:12:43)
npm ERR! Test failed. See above for more details.
npm ERR! not ok code 0
I updated the npm test command, should work now
When I run:
I get this output:
When I run
prova
from inside my working directory, I get: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!