title: Angular 5 unit testing failing even with module imports
body: <p>After running <code>ng test</code>, my Angular 5 app keeps returning errors like</p>
  
  <pre><code>Can't bind to 'routerLink' since it isn't a known property of 'button'.
  </code></pre>
  
  <p>and</p>
  
  <pre><code>Can't bind to 'ngModel' since it isn't a known property of 'select'.
  </code></pre>
  
  <p>It was generated by Angular-CLI.</p>
  
  <p>Going in to my <code>app.component.spec.ts</code> file...</p>
  
  <pre><code>import { RouterTestingModule } from '@angular/router/testing'
  import { AppComponent } from './app.component'
  import { FormsModule, ReactiveFormsModule } from '@angular/forms'
  import { UserService } from './user-account/user.service'
  
  describe('AppComponent', () =&gt; {
    beforeEach(() =&gt; {
      TestBed.configureTestingModule({
        imports: [
          RouterTestingModule,
          FormsModule,
          ReactiveFormsModule
        ],
        declarations: [
          AppComponent
        ],
        providers: [
          UserService
        ]
      })
      TestBed.compileComponents()
    })
  
    it('should create the app', async(() =&gt; {
      const fixture = TestBed.createComponent(AppComponent)
      const app = fixture.debugElement.componentInstance
      expect(app).toBeTruthy()
    }))
  
    it(`should have as title 'app works!'`, async(() =&gt; {
      const fixture = TestBed.createComponent(AppComponent)
      const app = fixture.debugElement.componentInstance
      expect(app.title).toEqual('app works!')
    }))
  
    it('should render title in a h1 tag', async(() =&gt; {
      const fixture = TestBed.createComponent(AppComponent)
      fixture.detectChanges()
      const compiled = fixture.debugElement.nativeElement
      expect(compiled.querySelector('h1').textContent).toContain('app works!')
    }))
  })
  </code></pre>
  
  <p>Since I'm importing the <code>FormsModule</code> and <code>RouterTestingModule</code>, I shouldn't be seeing these errors, right? I've closed and re-ran the test after saving but that has not fixed it either.</p>