This is a problem of the new Angular Cli. Run your test with –sourcemaps=false and you will get the right error messages. See details here: https://github.com/angular/angular-cli/issues/7296 EDIT: Shorthand for this is: ng test -sm=false As of angular 6 the command is: ng test –source-map=false
Because in unit tests you want to test the component mostly isolated from other parts of your application, Angular won’t add your module’s dependencies like components, services, etc. by default. So you need to do that manually in your tests. Basically, you have two options here: A) Declare the original NavComponent in the test describe(‘AppComponent’, … Read more
You need to import RouterTestingModule when setting up the test module. /* tslint:disable:no-unused-variable */ import { async, ComponentFixture, TestBed } from ‘@angular/core/testing’; import { By } from ‘@angular/platform-browser’; import { DebugElement } from ‘@angular/core’; import { RouterTestingModule } from ‘@angular/router/testing’; import { MyNewComponentComponent } from ‘./my-new-component.component’; describe(‘MyNewComponentComponent’, () => { let component: MyNewComponentComponent; let fixture: … Read more
This is fixed by: a) adding schemas: [ CUSTOM_ELEMENTS_SCHEMA ] to every component or b) adding import { NgModule, CUSTOM_ELEMENTS_SCHEMA } from ‘@angular/core’; and schemas: [ CUSTOM_ELEMENTS_SCHEMA ], to your module.