Karma tests not running

[melo0187]

From what I understand angular-fullstack generates both server tests for mocha and client tests for karma. For a newly generated app - after fixing both Gruntfile.js (see #247) and karma.conf.js (see #248) - I get following error when running grunt test :

[...]
Running "karma:unit" (karma) task
INFO [karma]: Karma v0.10.10 server started at http://localhost:8080/
INFO [launcher]: Starting browser PhantomJS
INFO [PhantomJS 1.9.7 (Linux)]: Connected on socket uyLE9920uagXDkUA7XIC
PhantomJS 1.9.7 (Linux): Executed 0 of 0 ERROR (0.149 secs / 0 secs)
Warning: Task "karma:unit" failed. Use --force to continue.

Aborted due to warnings.
[...]

It's strange to read Executed 0 of 0 since from what I understand there is a unit test. Does this mean that karma is failing to prepare test execution? How can I further investigate?

Thanks in advance!

[deebloo]

I am having the same problem. Even after fixing the couple issues in the latest update with the incorrect file path and syntax error I am getting the same issue.

[deebloo]

I think i may have found the solution. if I include the following in the karma config file the tests are running correctly.

files: [
      '../app/bower_components/angular/angular.js',
      '../app/bower_components/angular-mocks/angular-mocks.js',
      '../app/bower_components/angular-resource/angular-resource.js',
      '../app/bower_components/angular-cookies/angular-cookies.js',
      '../app/bower_components/angular-sanitize/angular-sanitize.js',
      '../app/bower_components/angular-route/angular-route.js',
      '../app/scripts/*.js',
      '../app/scripts/**/*.js',
      'client/spec/**/*.js'
]

[melo0187]

I can confirm @DannyBlueDesign's solution. I copy-pasted the paths to the files array in the karma config and the test for MainCtrl runs (and fails for me, because I altered MainCtrl without adapting it's test...).

I did not test whether or not all paths are required and can not tell if this is the right way to solve the problem or not, since I'm new to karma (and test's in web development in general).

But for now it does the trick for me and I can start fixing my test, so thanks @DannyBlueDesign!

[deebloo]

TEST ALL THE THINGS!!!!!

[JaKXz]

It's odd that snippet wasn't already there, my project built with an older version of the had it. @melo0187 I'm guessing you're using v.1.4.3?

[melo0187]

@JaKXz yes I am using v.1.4.3 of generator-angular-fullstack, installed globally with npm.

[deebloo]

That is how I found something to fix it. I looked through an older build I had done to compare.

[brandon-arnold]

I'm having the same problem, and unless I'm missing something, the above solution by DannyBlueDesign doesn't fix it. Can someone point in the right direction? It happens on both Fedora and Windows. Even the verbose output doesn't make sense, because the karma.conf.js file lists a number of files, and they all exist in the project directories.

Here's the verbose output in Windows. The punchline is that everything seems to go fine, but it says File: [no files] on the karma init, followed by "Executed 0 of 0 ERROR":

C:\Users\arnoldb\src\node\bacom>grunt karma:unit --verbose
Initializing
Command-line options: --verbose

Reading "Gruntfile.js" Gruntfile...OK

Registering Gruntfile tasks.

Registering "grunt-shell-spawn" local Npm module tasks.
Reading C:\Users\arnoldb\src\node\bacom\node_modules\grunt-shell-spawn\package.j
son...OK
Parsing C:\Users\arnoldb\src\node\bacom\node_modules\grunt-shell-spawn\package.j
son...OK
Loading "shell.js" tasks...OK
+ shell
Initializing config...OK
Loading "Gruntfile.js" tasks...OK
+ build, default, express-keepalive, serve, server, test, wait

Running tasks: karma:unit

Loading "grunt-karma

Registering "C:\Users\arnoldb\src\node\bacom\node_modules\grunt-karma\tasks" tas
ks.
Loading "grunt-karma.js" tasks...OK
+ karma
>> Plugin loaded.

Running "karma:unit" (karma) task
Verifying property karma.unit exists in config...OK
File: [no files]
Options: background=false
INFO [karma]: Karma v0.12.22 server started at http://localhost:8080/
INFO [launcher]: Starting browser PhantomJS
INFO [PhantomJS 1.9.7 (Windows 7)]: Connected on socket z4Kqb_4Gf-D7TSMKL7uX wit
h id 48428311
PhantomJS 1.9.7 (Windows 7): Executed 0 of 0 ERROR (0.002 secs / 0 secs)
Warning: Task "karma:unit" failed. Use --force to continue.

Aborted due to warnings.


Execution Time (2014-08-20 16:11:12 UTC)
loading tasks  757ms  ■■■■■■ 13%
karma:unit      5.2s  ■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■ 87%
Total 6s

Following is my karma.conf.js in the project root:

// Karma configuration
// http://karma-runner.github.io/0.10/config/configuration-file.html

module.exports = function(config) {
  config.set({
    // base path, that will be used to resolve files and exclude
    basePath: '',

    // testing framework to use (jasmine/mocha/qunit/...)
    frameworks: ['jasmine'],

    // list of files / patterns to load in the browser
    files: [
      'client/bower_components/jquery/dist/jquery.js',
      'client/bower_components/angular/angular.js',
      'client/bower_components/angular-mocks/angular-mocks.js',
      'client/bower_components/angular-resource/angular-resource.js',
      'client/bower_components/angular-cookies/angular-cookies.js',
      'client/bower_components/angular-sanitize/angular-sanitize.js',
      'client/bower_components/angular-bootstrap/ui-bootstrap-tpls.js',
      'client/bower_components/angular-ui-router/release/angular-ui-router.js',
      'client/bower_components/lodash/dist/lodash.compat.js',
      'client/app/app.coffee',
      'client/app/**/*.coffee',
      'client/components/**/*.coffee',
      'client/app/**/*.html',
      'client/components/**/*.html'
    ],

    preprocessors: {
      '**/*.jade': 'ng-jade2js',
      '**/*.html': 'html2js',
      '**/*.coffee': 'coffee',
    },

    ngHtml2JsPreprocessor: {
      stripPrefix: 'client/'
    },

    ngJade2JsPreprocessor: {
      stripPrefix: 'client/'
    },

    // list of files / patterns to exclude
    exclude: [],

    // web server port
    port: 8080,

    // level of logging
    // possible values: LOG_DISABLE || LOG_ERROR || LOG_WARN || LOG_INFO || LOG_DEBUG
    logLevel: config.LOG_INFO,


    // enable / disable watching file and executing tests whenever any file changes
    autoWatch: false,


    // Start these browsers, currently available:
    // - Chrome
    // - ChromeCanary
    // - Firefox
    // - Opera
    // - Safari (only Mac)
    // - PhantomJS
    // - IE (only Windows)
    browsers: ['PhantomJS'],


    // Continuous Integration mode
    // if true, it capture browsers, run tests and exit
    singleRun: false
  });
};

[kingcody]

@brandon-arnold, excuse me for my ignorance(?) but I was wondering what version of the generator you were using?

[brandon-arnold]

Thanks, Cody: I've just updated, and the version is 2.0.10, after having updated.

-Brandon

[kingcody]

@brandon-arnold are you still having the issue after updating to the new version?

[brandon-arnold]

@kingcody: Yep. any idea where I can find a more verbose debug output?