-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
V1.0.0 does NOT console.log() to the terminal, only logs in the browser's console #2187
V1.0.0 does NOT console.log() to the terminal, only logs in the browser's console #2187
Comments
thank you very much @dignifiedquire |
You are welcome :) Release should go out in the next hours |
I'm still having this issue on module.exports = function(config) {
config.set({
logLevel: config.LOG_DEBUG,
// base path that will be used to resolve all patterns (eg. files, exclude)
basePath: '../',
// frameworks to use
// available frameworks: https://npmjs.org/browse/keyword/karma-adapter
frameworks: ['mocha'],
files: [
// only specify one entry point
// and require all tests in there
'test/index.js'
],
// list of files to exclude
exclude: [
],
preprocessors: {
// add webpack as preprocessor
'test/index.js': ['webpack']
},
// test results reporter to use
// possible values: 'dots', 'progress'
// available reporters: https://npmjs.org/browse/keyword/karma-reporter
reporters: ['mocha'],
// web server port
port: 9876,
// enable / disable colors in the output (reporters and logs)
colors: true,
// level of logging
// possible values: config.LOG_DISABLE || config.LOG_ERROR || config.LOG_WARN || config.LOG_INFO || config.LOG_DEBUG
logLevel: config.LOG_INFO,
// enable / disable watching file and executing tests whenever any file changes
autoWatch: false,
// start these browsers
// available browser launchers: https://npmjs.org/browse/keyword/karma-launcher
browsers: ['PhantomJS'],
// Continuous Integration mode
// if true, Karma captures browsers, runs the tests and exits
singleRun: true,
// Concurrency level
// how many browser should be started simultaneous
concurrency: Infinity,
webpack: karmaWebpackConfig,
webpackMiddleware: {
// webpack-dev-middleware configuration
// i. e.
noInfo: true
},
client: {
captureConsole: true
}
});
}; |
@leoselig can you try with a different browser? |
@dignifiedquire I just tried with Chrome, same behavior Details: I ran:
|
It works for me though. I just tried Karma@1.1.0 and it console logs both, to the terminal and the browser's console. Here is my karma.conf.js. (You may have to explicitly add the launchers to the plugins:[ ] array in the karma.conf file)
|
Should be resolved by #2220 |
Expected behavior :
console.log('hello world') should log to the terminal when used with the karma-phantomjs-launcher. The previous version V - 0.13.22 logs to the terminal fine
Actual behavior:
does NOT console.log() to the terminal. logs only to the browser's console (chrome's console when karma-chrome-launcher is used)
Enviroment Details
karma --version
): V 1.0.0karma.config.js
fileSteps to reproduce the behaviour
1.Karma with Jasmine
2.Chrome and PhatomJS as the browsers
3.Console Logs fine in Chrome, but NOT in the terminal, the previous version of Karma V 0.13.22 works fine
4. And oh !... I'm using Mac
The text was updated successfully, but these errors were encountered: