angular-cli: ng test not working after upgrade to 6.0.0

I just ran into this as well (Executed 0 of 0 ERROR) after upgrading to Angular 6 on a project where tests previously ran successfully. I compared the test.ts file in my project versus a new project generated with the Angular 6 CLI, and noticed a lot of additional imports (import 'core-js/es7/reflect', import 'zone.js/dist/jasmine-patch'), etc in my project. I replaced these with:

import 'zone.js/dist/zone-testing';

and my tests started executing again. It definitely seems like an error message is getting swallowed somewhere.

I’ve done some more investigation. My Karma entrypoint file (which I had renamed from src/test.ts to ui/main.karma.ts; all of my .ts files live in ui rather than src) does not seem to be getting executed in the way I’d expect: none of the console.error statements I place in that file ever show up in the console or terminal output (they do show up in the terminal output if I do the same thing in a clean ng new project.)

I confirmed that my main.karma.ts file is correctly referenced from the angular.json test/main option, and I confirmed that compilation fails if I change the “main” attribute to point to a nonexistent filename.

I confirmed that my *.spec.ts files are detected and included by Karma. The generated _karma_webpack_/main.js file available when running Karma contains a var map = {...} line section which maps my spec files to their workspace-relative paths, and the tests themselves show up in that file.

My suspicion is still that something is going wrong with the execution of my Karma main entrypoint file, since like I mentioned, any console.error or other logging statements I add to that file are not showing up in my terminal output. However, that file is very simple and is identical to the test.ts provided out-of-the-box by Angular CLI, so I’m still not sure what the issue is.

I’ve got the same problem. Karma is running but no tests are executed.

It looks like test.ts is not loaded

Hey all, thanks for the reports. I think I know what was happening. It was two things together:

• AngularFire2 was importing zone directly (https://github.com/angular/angularfire2/issues/1597). This caused the “Zone already loaded.” message.
• the Angular CLI build system was splitting the common parts of polyfills and test but not loading the common bits. This resulted in no error messages and no tests ran.

The first problem was fixed in https://github.com/angular/angularfire2/pull/1599 and released in angularfire2@5.0.0-rc.8. The second problem has a fix incoming in https://github.com/angular/devkit/pull/993.

@herkulano I got your repro to work by manually applying the changes in my PR and updating to angularfire2@5.0.0-rc.8.

If you want to try this yourself, open node_modules/@angular-devkit/build-angular/src/angular-cli-files/models/webpack-configs/test.js and replace

chunks: buildOptions.commonChunk ? 'all' : 'initial',`

with

chunks: (chunk) => chunk.name !== "polyfills",

@Ristaaf your repro seems to work fine if I add import 'zone.js/dist/zone-patch-rxjs'; after import 'zone.js/dist/zone'; .

In my situation I had one spec file that silently failed the whole test run. After commenting out this spec, I was able to run tests again.

To find the specific test, I ran ls src/**/*.spec.ts | grep -o ".........$" | cut -d. -f1 | sort | uniq to get the previous letter before “.spec.ts” part. Then I added these letters. one by one, to regular expression in test.ts file, like a\.spec\.ts, then (a|b)\.spec\.ts etc. At the beginning, I run more and more tests successfully, until the regex included corrupted test. For me, the last letter added was ‘e’, so it was either service or pipe specification.

Subsequently, I was able to find autogenerated service test, that caused the error. I am pretty sure, that the error was in beforeEach part, however I can’t figure out the exact reason.

Hope my comment helps someone.

I got this same issue when using ng upgrade when upgrading to angular 6 on a cli project.

@herkulano it gave you no pointers because of the problem I am fixing in angular/devkit#993.

the Angular CLI build system was splitting the common parts of polyfills and test but not loading the common bits. This resulted in no error messages and no tests ran.

@WilliamChelman this method did expose an issue with my paths which are defined in tsconfig.json but were not being defined in the tsconfig.spec.json, this was not an issue in Angular 5.x. I have updated tsconfig.spec.json with those now as well:

 "paths": {
      "rxjs-compat": ["rxjs-compat.mock.ts"],
      "@app/*": ["app/*"],
      "@env/*": ["environments/*"]
    }

The only change seems to be an addition of a SUCCESS entry in the output:

Chrome 66.0.3359 (Mac OS X 10.13.4): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Chrome 66.0.3359 (Mac OS X 10.13.4): Executed 0 of 0 ERROR (0.02 secs / 0 secs)

I am surprised no one from the team have weighed in on this as yet, not even to merely label the issue 😐

If that might help, for our configuration it was the presence of rxjs-compat while testing that made everything fail (well, 0 of 0 executed), so in tsconfig.spec.json we added

"compilerOptions": {
        "paths": {
            "rxjs-compat": ["rxjs-compat.mock.ts"],
         }
}

where rxjs-compat.mock.ts is just

console.warn('False rxjs-compat loaded for testing, you should remove this whenever possible');

I have the same issue. I’ve managed to get it to work simply by removing and adding the tests again. It worked without changing any configuration. In my case, I’ve pinpointed the tests down to 3, as soon as I turn any of them on again it throws the dreaded Executed 0 of 0 ERROR.

My guess is that there’s some problem in the CLI that it doesn’t surface errors and fails silently.

In my case problem was caused by rxjs. In polyfills.ts I had imports like ‘rxjs/add/operator/map’ I could build and run app without any problem but test won’t work.

After removing old operators (and some refactoring to made it work) tests started to work again

I’ve checked code generated by jasmine.

All specs are present but none of them are loaded.

Could be related to https://github.com/angular/angularfire2/issues/1597

Downgrading firebase and angularfire2 fixes it:

"angularfire2": "5.0.0-rc.6",
"firebase": "~4.12",

I’m running into a similar issue on @angular/cli 6.0.0. For me, the error line looks like Chrome 66.0.3359 (Linux 0.0.0): Executed 0 of 0 ERROR (0.009 secs / 0 secs). Similar to @DominicBoettger, the previous behavior for my project was that the tests were found and executed successfully. I’m having trouble troubleshooting this; no errors appear in my Chrome console when running the tests, and changing the Karma log level to DEBUG doesn’t show any obvious issues. I tried futzing around with the dependency versions of Karma and Jasmine, thinking maybe I had upgraded them to incompatible versions, but that did not yield any solutions either. I’ve looked at the source changes made to my files as part of upgrading to Angular v6, but haven’t been able to identify any leads. Also, I’m not even seeing the npm ERR! messages that @DominicBoettger posted. The Executed 0 of 0 ERROR (0.009 secs / 0 secs) is the last line of the output for me before ng test finishes.