Angular-cli: Build Works, But Cannot Run "ng test"

Created on 30 Aug 2017  路  4Comments  路  Source: angular/angular-cli

Bug Report or Feature Request (mark with an x)

- [X ] bug report -> please search issues before submitting
- [ ] feature request

Versions.

@angular/cli: 1.1.2
node: 8.1.0
os: darwin x64
@angular/animations: 4.2.3
@angular/common: 4.2.3
@angular/compiler: 4.2.3
@angular/core: 4.2.3
@angular/forms: 4.2.3
@angular/http: 4.2.3
@angular/platform-browser: 4.2.3
@angular/platform-browser-dynamic: 4.2.3
@angular/router: 4.2.3
@angular/cli: 1.1.2
@angular/compiler-cli: 4.2.3
@angular/language-service: 4.2.3

Repro steps.

Run ng build or ng serve and the app works great. Run ng test and tests do not run...errors are below.
I can provide a sample repo if needed. Just need to strip some identifying info out of some files.
I've tried ng newing a project on this exact machine and had no issues running ng test. Unfortunately, this project was set aside for a while. When I came back to it today, tests would not run. It would be time-consuming to port everything to the latest version (long term stability is always appreciated).

The log given by the failure.

 10% building modules 1/1 modules 0 active29 08 2017 16:40:22.015:WARN [karma]: No captured browser, open http://localhost:9876/
29 08 2017 16:40:22.024:INFO [karma]: Karma v1.7.0 server started at http://0.0.0.0:9876/
29 08 2017 16:40:22.025:INFO [launcher]: Launching browser Chrome with unlimited concurrency
29 08 2017 16:40:22.030:INFO [launcher]: Starting browser Chrome                                                                                                             ERROR in /Users/user/ng2-sandbox/node_modules/@angular/core/src/testability/testability.d.ts (41,33): Cannot find name 'Node'.

ERROR in /Users/user/ng2-sandbox/node_modules/rxjs/observable/FromEventObservable.d.ts (11,39): Cannot find name 'EventTarget'.

ERROR in /Users/user/ng2-sandbox/node_modules/rxjs/observable/FromEventObservable.d.ts (11,103): Cannot find name 'NodeList'.

ERROR in /Users/user/ng2-sandbox/node_modules/rxjs/observable/FromEventObservable.d.ts (11,114): Cannot find name 'HTMLCollection'.

ERROR in /Users/user/ng2-sandbox/node_modules/rxjs/observable/dom/AjaxObservable.d.ts (16,23): Cannot find name 'XMLHttpRequest'.

ERROR in /Users/user/ng2-sandbox/node_modules/rxjs/observable/dom/AjaxObservable.d.ts (77,59): Cannot find name 'Event'.

ERROR in /Users/user/ng2-sandbox/node_modules/rxjs/observable/dom/AjaxObservable.d.ts (82,13): Cannot find name 'Event'.

ERROR in /Users/user/ng2-sandbox/node_modules/rxjs/observable/dom/AjaxObservable.d.ts (97,20): Cannot find name 'Event'.

ERROR in /Users/user/ng2-sandbox/node_modules/rxjs/observable/dom/AjaxObservable.d.ts (98,10): Cannot find name 'XMLHttpRequest'.

ERROR in /Users/user/ng2-sandbox/node_modules/rxjs/observable/dom/AjaxObservable.d.ts (108,32): Cannot find name 'Event'.

ERROR in /Users/user/ng2-sandbox/node_modules/rxjs/observable/dom/AjaxObservable.d.ts (108,44): Cannot find name 'XMLHttpRequest'.

ERROR in /Users/user/ng2-sandbox/node_modules/rxjs/observable/dom/AjaxObservable.d.ts (119,10): Cannot find name 'XMLHttpRequest'.

ERROR in /Users/user/ng2-sandbox/node_modules/rxjs/observable/dom/AjaxObservable.d.ts (124,39): Cannot find name 'XMLHttpRequest'.

ERROR in /Users/user/ng2-sandbox/node_modules/rxjs/observable/dom/AjaxObservable.d.ts (132,22): Cannot find name 'XMLHttpRequest'.

ERROR in /Users/user/ng2-sandbox/node_modules/rxjs/observable/dom/WebSocketSubject.d.ts (10,29): Cannot find name 'MessageEvent'.

ERROR in /Users/user/ng2-sandbox/node_modules/rxjs/observable/dom/WebSocketSubject.d.ts (11,33): Cannot find name 'Event'.

ERROR in /Users/user/ng2-sandbox/node_modules/rxjs/observable/dom/WebSocketSubject.d.ts (12,34): Cannot find name 'CloseEvent'.

ERROR in /Users/user/ng2-sandbox/node_modules/rxjs/observable/dom/WebSocketSubject.d.ts (15,63): Cannot find name 'WebSocket'.

ERROR in /Users/user/ng2-sandbox/node_modules/rxjs/observable/dom/WebSocketSubject.d.ts (27,13): Cannot find name 'WebSocket'.

ERROR in /Users/user/ng2-sandbox/node_modules/rxjs/observable/dom/WebSocketSubject.d.ts (28,32): Cannot find name 'Event'.

ERROR in /Users/user/ng2-sandbox/node_modules/rxjs/observable/dom/WebSocketSubject.d.ts (29,33): Cannot find name 'CloseEvent'.

ERROR in /Users/user/ng2-sandbox/node_modules/rxjs/observable/dom/WebSocketSubject.d.ts (32,63): Cannot find name 'WebSocket'.

ERROR in /Users/user/ng2-sandbox/node_modules/rxjs/observable/dom/WebSocketSubject.d.ts (36,23): Cannot find name 'MessageEvent'.

ERROR in /Users/user/ng2-sandbox/node_modules/@angular/http/src/body.d.ts (32,13): Cannot find name 'Blob'.

ERROR in /Users/user/ng2-sandbox/node_modules/@angular/http/src/interfaces.d.ts (75,30): Cannot find name 'FormData'.

ERROR in /Users/user/ng2-sandbox/node_modules/@angular/http/src/interfaces.d.ts (75,55): Cannot find name 'Blob'.

ERROR in /Users/user/ng2-sandbox/node_modules/@angular/http/src/base_response_options.d.ts (35,43): Cannot find name 'Blob'.
29 08 2017 16:41:22.034:WARN [launcher]: Chrome have not captured in 60000 ms, killing.
29 08 2017 16:41:22.148:INFO [launcher]: Trying to start Chrome again (1/2).
29 08 2017 16:42:22.151:WARN [launcher]: Chrome have not captured in 60000 ms, killing.

Desired functionality.

I just want my unit tests to run. That's it.

Most helpful comment

Heya, errors of that sort usually mean you need to update src/tsconfig.spec.json to include the necessariy libs. Have a look at https://github.com/angular/angular-cli/wiki/stories-1.0-update#one-tsconfig-per-app for details about this.

All 4 comments

+1, cannot run ng test !

Heya, errors of that sort usually mean you need to update src/tsconfig.spec.json to include the necessariy libs. Have a look at https://github.com/angular/angular-cli/wiki/stories-1.0-update#one-tsconfig-per-app for details about this.

Hey @filipesilva, that solved my problem. Thanks for your help...I would have never figured that out on my own!

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_This action has been performed automatically by a bot._

Was this page helpful?
0 / 5 - 0 ratings