Messages written to console.log don't show up in the terminal

[demisx]

Hi. I am using karma server to run my mocha unit tests for an angular app. The problem I am having is that messages that I write inside each it to console.log don't show up in the terminal. They do show up, however, if I simply run mocha [unit_test_file_name].js at command line. Am I missing something in the configuration? Here are my files:

// gulfile.js
karma = require('karma').server,
gulp.task('unit', function (done) {
  karma.start({
    configFile: __dirname + '/config/unit/karma-unit.conf.js',
    singleRun: true
  }, done);
});

// karma-unit-conf
module.exports = function(config) {
  config.set({

    basePath: '../../',
    autoWatch: false,
    frameworks: ['mocha', 'chai', 'sinon-chai', 'chai-as-promised'],
    // frameworks: ['mocha'],
    browsers: ['PhantomJS'],

    files: [
      'bower_components/angular/angular.js',
      'bower_components/lodash/dist/lodash.js',
      'app/**/*.coffee'
    ],

    plugins: [
      'karma-chrome-launcher',
      'karma-firefox-launcher',
      'karma-phantomjs-launcher',
      'karma-script-launcher',
      'karma-mocha',
      'karma-chai-plugins',
      'karma-coffee-preprocessor'
    ],

    preprocessors: {
      '**/*.coffee': ['coffee']
    },

    coffeePreprocessor: {
      options: {
        bare: true,
        sourceMap: false
      },
      transformPath: function(path) {
        return path.replace(/\.coffee$/, '.js');
      }
    },

    logLevel: config.LOG_DEBUG,

    client: {
      mocha: {
        bail: true
      }
    }
  });
};

Thank you!

[demisx]

I've noticed that I gain the ability to see written to console messages in my terminal back when I comment out the client property from the config object, i.e.:

// karma-unit-conf
module.exports = function(config) {
  config.set({
   ... ... ...
    logLevel: config.LOG_DEBUG,

    //  client: {
    //  mocha: {
    //     bail: true
    //   }
    // }
  });
};

Does this make sense?

[pkozlowski-opensource]

@demisx I would be keen to help out with this issue but there are just way to many dependencies in your project to do it in an efficient manner. Could you please create a minimal repository that exposes the issue? Like remove all the plugins / config options that are not essential to reproducing the issue?

We just basically need to have a minimal reproduce scenario that demonstrates an issue in one of the karma plugins. This will make the issue resolution faster. Thnx!

[demisx]

@pkozlowski-opensource I understand. Here is a stripped down repo to replicate this issue:
https://github.com/demisx/karma-mocha-console.

Instructions are in the readme file. Please let me know if there is anything else I can help with troubleshooting this issue.

[maksimr]

@demisx hi!

Put captureConsole to property client in karma.conf.js:

    client: {
      captureConsole: true,
      mocha: {
        bail: true
      }
    }

This problem relate to Karma and we have issue.
Thanks

[demisx]

Hi there. Indeed, this fixed the problem. Would be great if docs mentioned this option. I'll see if I can contribute to it.

[alexmgrant]

🍺

[winnemucca]

is the mocha object necessary to run this? I cannot get this option to run with jasmine.

[maksimr]

@winnemucca no, It should work without mocha object

[blackmjck]

Likewise, adding the client/captureConsole object doesn't fix the issue for me (also using Jasmine)

[AshCoolman]

Console.logs in my mocha tests are not showing up in terminal with

  logLevel: config.LOG_DEBUG,
  client: {
    captureConsole: true,
    mocha: {
      bail: true
    }
  },

[dignifiedquire]

please make sure to use [email protected] there was a bug in 1.0

[IdahoEv]

UPDATE: karma-mocha-reporter should be emitting logs, but isn't due to a bug in karma. The fix for that bug has been merged, so it should start working again with the next release of karma. Consider my suggestion below an ugly workaround in the meantime. See references:
litixsoft/karma-mocha-reporter#67
karma-runner/karma#2220

In case anyone else is coming across this issue: one possible cause is that you have turned off karma's default reporter. karma's default reporter (called 'progress') captures and re-emits log lines. If you have specified any other reporters, the progress reporter gets turned off unless you re-specify it.

As a result, if your karma.conf.js has an entry like this (ours did), you won't see your console.log messages, because neither karma-mocha-reporter nor karma-coverage-reporter emit log lines:

reporters: ['mocha', 'coverage']

If you just include progress in the list, you should get your console.log messages back, though having both progress and mocha reporters is a bit of a visual mess.

reporters: ['progress', 'mocha', 'coverage']

[bkakadiya42]

karma version:1.1.1

have following in the config:

reporters: ['progress', 'mocha'],
logLevel: config.LOG_DEBUG,
client: {
  captureConsole: true,
  mocha: {
    bail: true
  }
},

karma.config.js
package.json

We are still not being able to see console.logs in the terminal output.

[anvish]

fix for PhantomJS:

        client: {
            config: {
                browserConsoleLogOptions: true
            }
        }

[danday74]

My logs work with ...
client: {
captureConsole: true
}

but I seem to be getting loads of logging statements from third party libs .... annoying!

[niksumeiko]

Had the same problem after switching to use only "verbose" reporter‌! After adding "progress" to the reporters array in karma.conf.js, Terminal started to display logs I was adding via console.log().

...
reporters: ['progress', 'verbose'],
...

With only "verbose" reporter, logs weren't displayed.

[madroneropaulo]

Could not make it work either, as a REALLY hacky workaround for Chrome, you can monkeypatch the window console.log function from a second document. Useful ONLY when you are desperate, have complex tests and want to debug your tests with Chrome.

function consoleLog(str) {
    var i = document.createElement('iframe');
    i.style.display = 'none';
    document.body.appendChild(i);
    window.console = i.contentWindow.console;
   //(<any> window).console = i.contentWindow.console; // for Typescript tests.
    console.log(str);
}

[stevemao]

Looks like this issue reappears in v1.5.0.
Downgrading to v1.4.1 fixed it.

[davidturissini]

If its a help to anyone experiencing this, it appears that console.warn and console.error still work as expected

[maksimr]

@stevemao @davidturissini Look at this issue maybe it's your case.

Thanks

[stevemao]

I like the ideas in that issue :) But I think think should be a breaking change if console.log by default doesn't show any messages.

[sdtsui]

As of v1.5.0, modifications on the client key do not solve this issue. For example: 👎

client: {
  captureConsole: true,
  mocha: {
    bail: true
  }
},

Modifying browserConsoleLogOptions: 👍 worked.

    browserConsoleLogOptions: {
      level: 'log',
      format: '%b %T: %m',
      terminal: true
    }

See issues: #2582 & #2228 for more info.

[pearldiver]

@sdtsui it works but it log all the messages twice, i still did not figure out how to make it once only.

[spencer-brown]

@sdtsui 's solution does not double-log for me. Thanks for your solution, @sdtsui !

[tiefling]

@sdtsui 's solution worked for me (once I put it in the right place)

[kylebake]

The solution provided by @sdtsui worked beautifully for me as well, thank you. Just throw the browserConsoleLogOptions into the karma.conf.js if you're having trouble on where to place it.

[smelted-code]

@sdtsui You're a hero among men. Thank you, sir.

[riegersn]

Im still unable to see console.log unless I have logLevel: config.LOG_DEBUG Is there no way around this?

[phil123456]

none of these work with karma 4.0 :-(

[collinkrawll]

Just going to add that some of the solutions posted here were actually breaking my karma config under the current version (4.0). Removing them as described here fixed it.

[phil123456]

I dont even have these...also my browser closes even using autowatch (brand new karma version)

module.exports = function (config) {
  config.set({
    basePath: '',
    frameworks: ['jasmine', '@angular/cli'],
    plugins: [
      require('karma-jasmine'),
      require('karma-chrome-launcher'),
      require('karma-jasmine-html-reporter'),
      require('karma-coverage-istanbul-reporter'),
      require('@angular/cli/plugins/karma')
    ],
    client:{
      clearContext: false // leave Jasmine Spec Runner output visible in browser
    },
    coverageIstanbulReporter: {
      reports: [ 'html', 'lcovonly' ],
      fixWebpackSourcePaths: true
    },
    angularCli: {
      environment: 'dev'
    },
    reporters: ['progress', 'kjhtml'],
    port: 9876,
    colors: true,
    logLevel: config.LOG_DEBUG,
    autoWatch: true,
    browsers: ['Chrome'], 
    singleRun: true, 
    customLaunchers: 
    { 
    	ChromeHeadless: 
    	{ 
    		base: 'Chrome', 
    		flags: [ 
//    			'--headless', 
    			'--disable-gpu', 
    			'--disable-translate', 
    			'--disable-extensions', 
    			'--remote-debugging-port=9222', 
    			'--single-run=false',
    			'--auto-watch'
    			], 
    	} 
    }
  });
};

[JonLevy]

I'm having this problem with Karma 4.0.1 and developing in NativeScript.

[juniorschen]

I'm having this problem with Karma 4.0.1 and developing in NativeScript.

I'm too