"WARN [karma]: No captured browser" message always appears

Expected behaviour

Should not see any warnings when starting karma

Actual behaviour

The following output appears after i run karma start

21 09 2016 18:28:21.960:WARN [karma]: No captured browser, open http://localhost:9876/
21 09 2016 18:28:21.970:INFO [karma]: Karma v1.3.0 server started at http://localhost:9876/
21 09 2016 18:28:21.970:INFO [launcher]: Launching browser Chrome with unlimited concurrency
21 09 2016 18:28:21.992:INFO [launcher]: Starting browser Chrome
21 09 2016 18:28:22.881:INFO [Chrome 53.0.2785 (Linux 0.0.0)]: Connected on socket /#OLx2oK-yFrqokDyYAAAA with id 52089739

Environment Details

• Karma version (output of karma --version): 1.3.0
• Relevant part of your karma.config.js file:

// Karma configuration
// Generated on Wed Sep 21 2016 18:16:01 GMT+0100 (BST)

module.exports = function(config) {
  config.set({
    basePath: '',
    frameworks: ['jasmine'],
    files: [
      '*.js'
    ],
    exclude: [
    ],
    preprocessors: {
    },
    reporters: ['progress'],
    port: 9876,
    colors: true,
    logLevel: config.LOG_INFO,
    autoWatch: true,
    browsers: ['Chrome'],
    singleRun: false,
    concurrency: Infinity
  })
}

Steps to reproduce the behaviour

1. create a new project, set up package.json with :

   "devDependencies": {
     "jasmine-core": "^2.5.2",
     "karma": "^1.3.0",
     "karma-chrome-launcher": "^2.0.0",
     "karma-jasmine": "^1.0.2"
   }
   

2. use the above karma.conf.js

3. create a dummy js file so karma has something to load (eg. test.js)

4. run karma start, and you should see a warning

[aleksspeaker]

Hey guys, Any updates on this issue?

[johnjbarton]

3.5 years and still no solution?

karma has worked fine for millions of tests over those 3.5 years. So perhaps there never was a problem here?

The “No captured browser” means karma can’t automatically test because it does not have a browser to launch tests in. I speculated on the cause, a deliberate config issue, above. Without further information there is nothing to do here.

I suggest opening a new issue with a complete description from a recent karma version and the output of --logLevel=DEBUG.