Fork

[mageddo]

Main difference

On original grunt-mocha-test if you have a mocha test that use console.log and configuration like that

mochaTest: {
  'coverage': {
    options: {
      reporter: 'html-cov',
      quiet: true,
      captureFile: 'unit-tests.html',
    },
    src: ['test.js']
  },
}

the test

describe('grunt-mocha-test', function() {
  it('should return 1', function(done) {
    console.log('It will out on report file');
    done();
  });
});

In this case the console output will be reported on report file, this fork fix it. To it work the reporter need to write on the runner.on('end') event

[pghalliday]

Haven't had a chance to check this out and see what's happening but did you notice that all the tests are failing?

[mageddo]

Aw.. It was very easy, sorry I will check it.

[mageddo]

How can I do tests, $ grunt?, I try run it on my terminal but all test fail too on 235554c

$ grunt 
0 passing (17s)
33 failing

[pghalliday]

Strange, that succeeded on Travis. What version of nodejs are you using?

[pghalliday]

hmm, just updated my node_modules and now get the same problem - somewhere an updated dependency has broken things

[pghalliday]

ok the problem was a change to the way blanket works for generating coverage when use strict is present. Have worked around it by removing the use strict

[pghalliday]

Yup now I only have 3 failing tests and they're all related to your changes. Can you update the tests to reflect what the new behaviour should be?

[mageddo]

I am using node 0.12.7. Fine, I will cover the tests and update the pull request, can I push with use strict removed?

[pghalliday]

Best would be to do:

git fetch origin master
git rebase origin/master

That way you pick up the changes I just made and can put your changes on top of that - there shouldn't be any conflicts AFAIK.

Don't worry about use strict - it shouldn't have been on in the first place

thanks

[mageddo]

Ok...