-
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.1.0 and v1.2.0 do not run any tests #2217
Comments
Same, but different env. ❯ karma start
30 06 2016 00:56:05.865:INFO [karma]: Karma v1.1.0 server started at http://localhost:9876/
30 06 2016 00:56:05.868:INFO [launcher]: Launching browser Chrome with unlimited concurrency
30 06 2016 00:56:05.877:INFO [launcher]: Starting browser Chrome
30 06 2016 00:56:06.924:INFO [Chrome 51.0.2704 (Mac OS X 10.11.5)]: Connected on socket /#PUznwnnYyUP5WpwSAAAA with id 37853966
Chrome 51.0.2704 (Mac OS X 10.11.5) ERROR
Uncaught TypeError: Cannot read property 'call' of undefined
at node_modules/mocha/mocha.js:707
npm ERR! Test failed. See above for more details. Testdescribe('test'), () => {
it('works'), () => {
// it works
}
} In my case, downgrading to 1.0 does not help. 30 06 2016 01:04:37.620:INFO [karma]: Karma v1.0.0 server started at http://localhost:9876/
30 06 2016 01:04:37.623:INFO [launcher]: Launching browser Chrome with unlimited concurrency
30 06 2016 01:04:37.630:INFO [launcher]: Starting browser Chrome
30 06 2016 01:04:38.762:INFO [Chrome 51.0.2704 (Mac OS X 10.11.5)]: Connected on socket /#-xyAZYJ_t7xKqlgKAAAA with id 99821804
Chrome 51.0.2704 (Mac OS X 10.11.5) ERROR
Uncaught TypeError: Cannot read property 'call' of undefined
at node_modules/mocha/mocha.js:707
npm ERR! Test failed. See above for more details. Nor does an older version. 30 06 2016 01:11:58.152:INFO [karma]: Karma v0.13.22 server started at http://localhost:9876/
30 06 2016 01:11:58.160:INFO [launcher]: Starting browser Chrome
30 06 2016 01:11:59.535:INFO [Chrome 51.0.2704 (Mac OS X 10.11.5)]: Connected on socket /#kmC-lF1fJcKQ3FYuAAAA with id 24896962
Chrome 51.0.2704 (Mac OS X 10.11.5) ERROR
Uncaught TypeError: Cannot read property 'call' of undefined
at /Users/kevinSuttle/Code/platform-ui-primitives/node_modules/mocha/mocha.js:707 karma.config.jsmodule.exports = function(config) {
config.set({
basePath: '',
frameworks: ['mocha'],
files: [
'test/index.test.js',
],
reporters: ['progress'],
port: 9876,
colors: true,
logLevel: config.LOG_INFO,
autoWatch: false,
browsers: ['Chrome'],
singleRun: true,
concurrency: Infinity,
})
} I noticed I don't get the error when I set
|
@oocx Are you using Babel 6 and/or Webpack 2.x? |
Babel 6 and Webpack 1.13.1 I'm compiling with TypeScript to ES2015 (so that I can use async/await in TypeScript), and then from ES2015 to ES5 with Babel. Here are my devDependencies:
|
I use same simple config as Kevin and my tests don't run either. I don't get any errors, karma just doesn't run my tests. My solution was also to add --auto-watch --no-single-run. I tried 0.13.22, 1.0.0 and 1.1.0 and behavior is the same in all of them. |
Same here. I had to switch back to |
For what it's worth, I tested on 1.0.0 and 1.10 and had the issue, but it's no longer there when I went back to 0.13.22. |
@jacquesdev What else changed in your package.json? |
Nothing else changed, I am setting up tests for the first time. When I tried running tests on 1+ I get the warning, but not on 0.13.22. Since I am just getting the warnings and no errors, I guess I don't have the exact same issue the other users are having. |
Same problem here, also using webpack. In my case it works in 1.0.0 but not 1.1.0 or 1.1.2
|
The original issue has been resolved in the latest version. @lukeapage can you open a new issue about your problem please? |
The problem is NOT fixed. Please reopen this issue. All you fixed is that the output no longer contains the promise warnings, which is not what this bug report was about. The problem is that karma is not running any tests!
|
@oocx can you please provide a repo that reproduces this error, all jasmine tests I have are running fine on the latest version. |
After updating other dependencies, karma 1.2 is working for me now. I don't know which combination of dependencies exactly has caused the problem. I updated from Angular RC5 to RC6 and during that update I also updated jasmine-core (to 2.5.0), zone.js (to 0.6.17), rxjs (to 5.0.0-beta.11) and several other dependencies. |
On Linux,
|
Saw this problem on Linux, karma 1.7.1, karma-jasmine 0.1.6. |
Expected behavior
Karma runs my tests
Actual behavior
I see the following output:
Enviroment Details
Karma.conf.js:
Steps to reproduce the behaviour
Karma works as expected with 1.0.0
The text was updated successfully, but these errors were encountered: