No Captured Browser when using with watch

Using the following config:

  grunt.initConfig({
    karma: {
      unit: {
        options: {
          autoWatch: false,
          singleRun: true,
        }
      },
      watch: {
        options: {
          autoWatch: false,
          singleRun: false
        },
        background: true,
      },
      options: {
        configFile: '<%= testFiles.karmaUnit %>',
        browsers: browsers || ['Chrome']
      }
    },

    watch: {
      karma: {
        files: ['karma.conf.js', 'src/main/resources/**/*.js', 'src/test/**/*.js'],
        tasks: ['karma:unit:run']
      },
      options: {
        atBegin: true
      }
    }
  });

  grunt.loadNpmTasks('grunt-karma');
  grunt.loadNpmTasks('grunt-contrib-watch');

  grunt.registerTask('testwatch', ['karma:watch:start', 'watch:karma']);

My goal is to have karma start up the background thread and then repeatedly run tests against it when files change. However, when I run ‘testwatch’, it appears the karma:unit:run tries to run before the Karma server really has had a chance to finish starting:

Running "karma:watch:start" (karma) task

Running "watch:karma" (watch) task
Waiting...OK

Running "karma:unit:run" (karma) task
[2014-01-06 12:11:25.495] [DEBUG] config - Loading config /Users/mhughes/ccad/development/firebird/core-plugins/silk/certificate-management/ui/karma.conf.js
No captured browser, open http://localhost:9876/

My browser does start and is connected to the aforementioned address, but it just appears to be a timing issue. If I modify a file after the initial startup, the tests run and are able to connect to the browser. That makes me think that ‘karma⌚start’ does not wait until the browser is truly up and connected.

[jcrben]

I see this warning although my tests seem to be running OK anyway.

[bierik]

Same problem here… does only occur when autowach is active