Getting "Executed 0 of 0 ERROR" in the console #753

marcobarbosa · 2013-09-23T09:41:41Z

Hi all,

I'm trying to use karma with jasmine-flight and require.js.

I have no tests in place, just want to get a normal "0 of 0 SUCESS" before getting started.

However this is ERROR is shown in my console:

INFO [karma]: Karma v0.10.2 server started at http://localhost:9876/
INFO [launcher]: Starting browser Chrome
INFO [Chrome 29.0.1547 (Mac OS X 10.8.5)]: Connected on socket YRMSwebi_lNtEYDnL0rk
Chrome 29.0.1547 (Mac OS X 10.8.5): Executed 0 of 0 ERROR (0.171 secs / 0 secs)

I have found similar issues but related to "Angular" not "Flight".

This is my karma.conf:

// Karma configuration
// Generated on Thu Sep 19 2013 16:31:19 GMT+0200 (CEST)

module.exports = function(config) {
  config.set({

    // base path, that will be used to resolve files and exclude
    basePath: '',

    // frameworks to use
    frameworks: ['requirejs', 'jasmine'],

    // list of files / patterns to load in the browser
    files: [
        '../bower_components/jasmine-flight/lib/jasmine-flight.js',
        '../bower_components/jasmine-jquery/lib/jasmine-jquery.js',

        {pattern: '*.js', included: false},
        {pattern: 'mixins/*.js', included: false},
        {pattern: 'data/*.js', included: false},
        {pattern: 'pages/*.js', included: false},
        {pattern: 'ui/**/*.js', included: false},
        {pattern: 'tests/spec/**/*.spec.js', included: false},

        // Entry point for karma.
        'tests/test-main.js'
    ],

    // list of files to exclude
    exclude: [
        '../bower_components/flight/lib/standalone/*.js'
    ],

    // test results reporter to use
    // possible values: 'dots', 'progress', 'junit', 'growl', 'coverage'
    reporters: ['dots'],


    // 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: true,


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


    // If browser does not capture in given timeout [ms], kill it
    captureTimeout: 5000,


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

    // report which specs are slower than 500ms
    // CLI --report-slower-than 500
    reportSlowerThan: 500,

    plugins: [
            'karma-jasmine',
            'karma-requirejs',
            'karma-chrome-launcher',
            'karma-safari-launcher'
        ]
  });
};

Is this a bug or am I doing something wrong?

The text was updated successfully, but these errors were encountered:

bolasblack · 2013-09-29T06:52:37Z

I've also got the same error.

result

INFO [karma]: Karma v0.10.2 server started at http://localhost:9876/
INFO [launcher]: Starting browser Chrome
INFO [Chrome 29.0.1547 (Mac OS X 10.8.5)]: Connected on socket dAmNUJiZMZvLa53AfORr
LOG: 'spec run'
Chrome 29.0.1547 (Mac OS X 10.8.5): Executed 0 of 0 ERROR (0.755 secs / 0 secs)

karma.conf.coffee

module.exports = (config) ->
  config.set

    plugins: [
      'karma-chai'
      'karma-mocha'
      'karma-chrome-launcher'
      'karma-coffee-preprocessor'
    ]

    # base path, that will be used to resolve files and exclude
    basePath: '../'

    frameworks: ['mocha', 'chai']

    # list of files / patterns to load in the browser
    files: [
      'public/js/vendor.js'
      'bower_components/angular-mocks/angular-mocks.js'
      'app/resources/**/*.coffee'
      'test/unit/**/*.spec.*'
    ]

    # list of files to exclude
    exclude: []

    preprocessors: {
      'app/resources/**/*.coffee': ['coffee']
      'test/unit/**/*.coffee': ['coffee']
    }

    # use dots reporter, as travis terminal does not support escaping sequences
    # possible values: 'dots', 'progress'
    # CLI --reporters progress
    reporters: ['progress']

    # web server port
    # CLI --port 9876
    port: 9876

    # enable / disable colors in the output (reporters and logs)
    # CLI --colors --no-colors
    colors: true

    # level of logging
    # possible values: config.LOG_DISABLE || config.LOG_ERROR || config.LOG_WARN || config.LOG_INFO || config.LOG_DEBUG
    # CLI --log-level debug
    logLevel: config.LOG_INFO

    # enable / disable watching file and executing tests whenever any file changes
    # CLI --auto-watch --no-auto-watch
    autoWatch: true

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

    # If browser does not capture in given timeout [ms], kill it
    # CLI --capture-timeout 5000
    captureTimeout: 20000

    # Auto run tests on start (when browsers are captured) and exit
    # CLI --single-run --no-single-run
    singleRun: false

    # report which specs are slower than 500ms
    # CLI --report-slower-than 500
    reportSlowerThan: 500

resources.spec.coffee

'use strict'

console.log 'spec run' # it's ok

describe "services", ->

  it "should error", ->
    console.log 'it should error' # not print
    'a'.should.equal 1

bolasblack · 2013-09-29T07:47:26Z

I resolved the error when I remove angular-scenario from vendor.js file.

Thanks stackoverflow: http://stackoverflow.com/questions/18366837/karma-not-running-tests

@marcobarbosa is it can help you?

marcobarbosa · 2013-09-30T13:11:39Z

@bolasblack No, since I'm not using Angular. Thanks anyway! :)

dignifiedquire · 2013-10-04T18:46:00Z

@marcobarbosa Do you have a github project I could look at? Or just a simple example that reproduces what you are seeing.

marcobarbosa · 2013-10-06T15:24:52Z

Sorry it's actually private so I can't share :(

I have updated the karma.conf above but just some paths - shouldn't interfere.

dignifiedquire · 2013-10-13T18:16:10Z

@marcobarbosa This looks like a problem loading the tests. Can you share the relevant parts of your test-main.js?

vojtajina · 2013-11-16T05:02:19Z

@marcobarbosa it's hard to help with this without seeing your files. It's more likely you are not including the test files or they are not executed. What is your test-main.js look like ?

marcobarbosa · 2013-11-16T08:37:12Z

Hi guys,

Sorry about this. I don't have access to the files (private) so I can't really paste them.

I know this is how my test-main.js was looking like then:

'use strict';

var tests = Object.keys(window.__karma__.files).filter(function (file) {
  return (/\.spec\.js$/.test(file));
});

requirejs.config({
  // Karma serves files from '/base'
  baseUrl: '/base',

  paths: {
    // required! don't remove this line
    flight: 'app/bower_components/flight',
    // ----------------------------------
    events: 'app/scripts/events',
    utils: 'app/scripts/utils',

    // Templating
    mustache: 'app/bower_components/mustache/mustache'
  },

  map: {
      '*': {
          'flight/component': 'app/bower_components/flight/lib/component',
          'flight/compose': 'app/bower_components/flight/lib/compose',
          'flight/lib/registry': 'app/bower_components/flight/lib/registry'
      },
  },

  shim: {
    'app/bower_components/flight/lib/index': {
      deps: ['jquery', 'es5shim', 'es5sham']
    }
  },

  // ask Require.js to load these files (all our tests)
  deps: tests,

  // start test run, once Require.js is done
  callback: window.__karma__.start
});

// jasmine.getFixtures().fixturesPath = 'base/test/fixtures';

marcobarbosa · 2013-11-16T08:37:26Z

Maybe this issue should be closed?

vojtajina · 2013-11-16T21:42:19Z

@marcobarbosa Did you figure this out?

Check console.log(tests); in your test-main.js, to make sure the tests are loaded.

mikew · 2013-12-30T07:40:38Z

I too am seeing this error. Not sure if it's because I'm using brunch and the tests are all wrapped in requires, but everything works fine and dandy loading the mocha test page in the browser, and running it with mocha-phantomjs.

https://github.com/mikew/brunch-flask

Given that I am using brunch, this isn't a huge deal, though I do like the auto-launching of the browsers and the console output.

mikew · 2013-12-30T08:06:26Z

Ah, trying out test'em lead me to the solution.

Remove mocha.css, mocha.js, chai.js from test/vendor/
Install karma-chai
Change frameworks to ['mocha', 'chai']

vojtajina · 2014-01-20T00:32:17Z

Yeah, you need the mocha framework because of the adapter (you could load mocha itself from your project as before and that would work.

Anyway, now Karma complains that you are missing an adapter, which would at least make it easier to debug. Closing.

ttencate · 2014-11-16T14:50:32Z

FWIW, I ran into this anonymous ERROR problem as well. It went away when I deleted my node_modules directory and re-ran npm install.

Since I'd been hacking around in modules' source code, I don't think this would happen during normal karma operation.

andrerpena · 2015-06-30T01:48:36Z

In case this helps anyone, I ran into this problem because my main test file has 2 describe but no it.

It was like this:

describe('Something abstract', function() {
    describe('Something specific', function() {
    });
});

And when I made it like this, it worked:

describe('Something abstract', function() {
    describe('Something specific', function() {
        it('Something', function() {
            assert.equal(1, 1);
        });
    });
});

axelson · 2016-01-19T22:03:25Z

For those still coming across this from searches the default behavior appears to have possibly switched so that having no tests causes an error: #1690

DevFacts · 2016-05-26T20:29:10Z

Hi guys!
Getting "Executed 0 of 0 ERROR" in the console (FIXED)

My config file name is (test.conf.js)

============================Code Start======================================
module.exports = function(config) {
config.set({

// 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: ['jasmine'],


// list of files / patterns to load in the browser
files: [
'../www/lib/angular/angular.js',
'../www/js/*.js',
'../www/lib/angular-mocks/angular-mocks.js',
'**/*.js'
],


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


// preprocess matching files before serving them to the browser
// available preprocessors: https://npmjs.org/browse/keyword/karma-preprocessor
preprocessors: {
},


// test results reporter to use
// possible values: 'dots', 'progress'
// available reporters: https://npmjs.org/browse/keyword/karma-reporter
reporters: ['progress'],


// 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: true,


// start these browsers
// available browser launchers: https://npmjs.org/browse/keyword/karma-launcher
browsers: ['Chrome'],


// Continuous Integration mode
// if true, Karma captures browsers, runs the tests and exits
singleRun: false,

// Concurrency level
// how many browser should be started simultaneous
concurrency: Infinity

})
}
==========================Code====END===============================
Explanation:-

files: [
'../www/lib/angular/angular.js',
'../www/js/.js',
'../www/lib/angular-mocks/angular-mocks.js',
'__/.js'
]

In this part, I always ignore. But here was the problem
My old code [ 'test//*.js' ] and new is [ '/*.js' ]

My project directory

Project22
-js
-css
-test (test folder)
-test.conf.js
-templates

I think it should work fine for you.

dummdidumm · 2017-10-26T15:55:09Z

I got this error while using Chrome (or ChromeHeadless) as browser + using typescript. This solution fixed it for me: angular/angular-cli#2125 (comment)

pmandapuram · 2017-12-13T12:24:51Z

Hi ,
I am written jasmine test cases to a method that get all attributes which are available in database
is it possible to test from jasmine test suite
and i am getting 0 specs and 0 failures when i am running the tests
Please help me to sort out this problem

johnjbarton · 2017-12-13T17:01:57Z

If you are using asynchronous code (promises), verify that you return a promise chain or call done().
Open the DEBUG window and use devtools to examine the test.

pmandapuram · 2017-12-14T08:50:23Z

thanks Johnjbarton

Drumstix42 · 2018-05-03T21:13:09Z

Anyone coming across this thread years later, as I did. I discovered there is a boolean you can set in the config object, failOnEmptyTestSuite
This let me setup a configuration without needing to define any test cases.

See: http://karma-runner.github.io/2.0/config/configuration-file.html

aj-r · 2018-06-20T18:35:47Z

Got this error when testing with typescript. The reason is because karma does not host typescript files by default. The solution was to add this to my karma config:

    mime: {
      "text/x-typescript": ["ts", "tsx"],
    },

yogeshwar1996 · 2018-06-21T03:05:22Z

Thanks @aj-r adding mime property to karma.conf.js helped me. Now my tests are executing

rupeshtiwari · 2018-09-12T16:53:20Z

In my case it was below line that I was missing bootstrap angular.

const app = bootstrapModule(getMockSettings());
(angular as any).lowercase = text => text.toLowerCase();
angular.bootstrap(document, [app ]);

collinkrawll · 2019-02-07T02:16:25Z

In my case, I was actually getting "Executed 0 of N ERROR". Simple tests would show in N but would never actually be executed. I removed each of my scripts and eventually narrowed it down to a jQuery(document).ready(... function that was throwing an exception that was being swallowed. I guess the tests were being registered but never got to execute (and the exception was being swallowed).

Kendsar · 2019-03-28T11:26:24Z

In my case I was trying to run

ng test

While I'am not running

npm start

And that's will not work and will show 0 specs, 0 failures ,of course.

cluzier · 2019-05-17T14:42:04Z

I resolved the error when I remove angular-scenario from vendor.js file.

Thanks stackoverflow: http://stackoverflow.com/questions/18366837/karma-not-running-tests

@marcobarbosa is it can help you?

can anyone else confirmed this worked for them before I do it myself?

vojtajina closed this as completed Jan 20, 2014

yggg mentioned this issue Oct 9, 2018

npm test error Executed 0 of 0 ERROR akveo/ngx-admin#1467

Open

loftyduck mentioned this issue Jun 21, 2023

[Snyk] Security upgrade log4js from 1.1.1 to 3.0.0 loftyduck/karma#11

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Getting "Executed 0 of 0 ERROR" in the console #753

Getting "Executed 0 of 0 ERROR" in the console #753

marcobarbosa commented Sep 23, 2013

bolasblack commented Sep 29, 2013

bolasblack commented Sep 29, 2013

marcobarbosa commented Sep 30, 2013

dignifiedquire commented Oct 4, 2013

marcobarbosa commented Oct 6, 2013

dignifiedquire commented Oct 13, 2013

vojtajina commented Nov 16, 2013

marcobarbosa commented Nov 16, 2013

marcobarbosa commented Nov 16, 2013

vojtajina commented Nov 16, 2013

mikew commented Dec 30, 2013

mikew commented Dec 30, 2013

vojtajina commented Jan 20, 2014

ttencate commented Nov 16, 2014

andrerpena commented Jun 30, 2015

axelson commented Jan 19, 2016

DevFacts commented May 26, 2016

dummdidumm commented Oct 26, 2017

pmandapuram commented Dec 13, 2017 •

edited

Loading

johnjbarton commented Dec 13, 2017

pmandapuram commented Dec 14, 2017

Drumstix42 commented May 3, 2018

aj-r commented Jun 20, 2018

yogeshwar1996 commented Jun 21, 2018

rupeshtiwari commented Sep 12, 2018

collinkrawll commented Feb 7, 2019

Kendsar commented Mar 28, 2019

cluzier commented May 17, 2019

Getting "Executed 0 of 0 ERROR" in the console #753

Getting "Executed 0 of 0 ERROR" in the console #753

Comments

marcobarbosa commented Sep 23, 2013

bolasblack commented Sep 29, 2013

bolasblack commented Sep 29, 2013

marcobarbosa commented Sep 30, 2013

dignifiedquire commented Oct 4, 2013

marcobarbosa commented Oct 6, 2013

dignifiedquire commented Oct 13, 2013

vojtajina commented Nov 16, 2013

marcobarbosa commented Nov 16, 2013

marcobarbosa commented Nov 16, 2013

vojtajina commented Nov 16, 2013

mikew commented Dec 30, 2013

mikew commented Dec 30, 2013

vojtajina commented Jan 20, 2014

ttencate commented Nov 16, 2014

andrerpena commented Jun 30, 2015

axelson commented Jan 19, 2016

DevFacts commented May 26, 2016

dummdidumm commented Oct 26, 2017

pmandapuram commented Dec 13, 2017 • edited Loading

johnjbarton commented Dec 13, 2017

pmandapuram commented Dec 14, 2017

Drumstix42 commented May 3, 2018

aj-r commented Jun 20, 2018

yogeshwar1996 commented Jun 21, 2018

rupeshtiwari commented Sep 12, 2018

collinkrawll commented Feb 7, 2019

Kendsar commented Mar 28, 2019

cluzier commented May 17, 2019

pmandapuram commented Dec 13, 2017 •

edited

Loading