issacg / mocha-bamboo-reporter Goto Github PK

I get the output double callback twice when I use the mocha-bamboo-reporter within my gulp mocha test run. The mocha.json is also not generated.

Without it everything works fine.

I am running protractor tests through Selenium Server on a number of browsers simultaneously.
The mocha bamboo reporter wirtes the results to mocha.json after each test. But when starting the next tests it removes that file. Which means only the results from the last test are being saved.

So I modified the reporter locally by reading the results, adding the new result and writing it back to the file.
This only works when running tests sequentially as 2 tests finishing at the same time would miss each other's results.

Is there any chance the bamboo reporter will be updated by supporting parallel runs?

May I suggest renaming the repository to mocha-bamboo-reporter? Would make more sense in reference to NPM registry.

I'm not sure why this happened yet, but the code in clean() is assuming that there is a stack property on test.err and it seems that isn't always there.

error   04-Mar-2015 17:35:54    /srv/bamboo-agent-home/xml-data/build-dir/WRTC-FBT0-JOB1/functional-browser-tests/node_modules/mocha-bamboo-reporter/lib/bamboo.js:74
error   04-Mar-2015 17:35:54        o.error = test.err.stack.toString();
error   04-Mar-2015 17:35:54                                 ^
error   04-Mar-2015 17:35:54    TypeError: Cannot call method 'toString' of undefined
error   04-Mar-2015 17:35:54        at clean (/srv/bamboo-agent-home/xml-data/build-dir/WRTC-FBT0-JOB1/functional-browser-tests/node_modules/mocha-bamboo-reporter/lib/bamboo.js:74:30)
error   04-Mar-2015 17:35:54        at Array.map (native)
error   04-Mar-2015 17:35:54        at Runner.<anonymous> (/srv/bamboo-agent-home/xml-data/build-dir/WRTC-FBT0-JOB1/functional-browser-tests/node_modules/mocha-bamboo-reporter/lib/bamboo.js:44:28)
error   04-Mar-2015 17:35:54        at Runner.emit (events.js:117:20)
error   04-Mar-2015 17:35:54        at Runner.uncaught (/srv/bamboo-agent-home/xml-data/build-dir/WRTC-FBT0-JOB1/functional-browser-tests/node_modules/mocha/lib/runner.js:563:8)
error   04-Mar-2015 17:35:54        at process.uncaught (/srv/bamboo-agent-home/xml-data/build-dir/WRTC-FBT0-JOB1/functional-browser-tests/node_modules/mocha/lib/runner.js:580:10)
error   04-Mar-2015 17:35:54        at process.emit (events.js:95:17)
error   04-Mar-2015 17:35:54        at process._fatalException (node.js:272:26)

Can you release the current master branch to npm? I have my project pointing at the commit that contains the change to allow a custom filename using MOCHA_FILE environment variable, but i'd like to just have it point at an npm version instead.

If there's anything you need to facilitate the release let me know and i'll do it.

Thanks!

When used with Bamboo 5.9.10 build 5921, the Bamboo UI displays

My random test should work should work

The test was written like this:

decribe( 'My random test', function () {
  it( 'shold work', function () {
    //...
  } );
} );

Not sure if this is a mocha-bamboo-reporter issue, though. 🍻