Branches on constructor not covered

Question

I am creating my unit tests with Jasmine and I have a question about the branch covered.

Does anyone know why the code part shows that the branches are not covered as we can see below?

This is the unit test:

describe('MyComponent', () => {
  let component: MyComponent;
  let fixture: ComponentFixture<MyComponent>;
  let myService: MyService;

  beforeEach(async(() => {
    TestBed.configureTestingModule({
      declarations: [ MyComponent ],
      imports: [ MaterializeModule, FormsModule, ReactiveFormsModule, HttpModule ],
      providers: [
        MyService,
        FormBuilder
      ]
    })
    .compileComponents();
  }));

  beforeEach(() => {
    fixture = TestBed.createComponent(MyComponent);
    component = fixture.componentInstance;
    slotsService = TestBed.get(MyService);
    fixture.detectChanges();
  });

  function updateForm(name, surname) {
    component.myForm.controls['name'].setValue(name);
    component.myForm.controls['surname'].setValue(name);
  }

  it('should create', () => {
    expect(component).toBeTruthy();
  });
}

show your unit test – Julia Passynkova Jun 29 '17 at 23:40 — Julia Passynkova, Jun 29 '17 at 23:40

score 8 · Answer 1 · answered Jun 30 '17 at 22:02

8

I've had the same issue for months from the moment I upgraded my projects to angular 4. Unfortunately it is a bug with the angular-cli version 1 and angular 4.

This bug is already logged in the angular-cli project: Test-coverage says that coverage is not 100%, but it truly is! #5871. Unfortunately at the moment, this issue is still open.

This is a snapshot from that logged issue, which matches the one you are asking about:

answered Jun 30 '17 at 22:02

Juan

6,125
3
30
31

I am facing the same issue – Aniruddha Das Aug 15 '17 at 15:41

score 1 · Answer 2 · answered Aug 29 '17 at 11:29

If you are facing this problem and , nevertheless, want to reach 100% branch coverage, there is at least a workaround available (see https://github.com/angular/angular-cli/issues/5526#issuecomment-324429322).

Simply add /* istanbul ignore next */ after the class export (without any line breaks):

export class InternalComponent {
    constructor(private authService: any) { 
    }
} /* istanbul ignore next */

score 0 · Answer 3 · answered Dec 14 '17 at 14:23

0

For Angular 2+ projects, this is now fixed if you upgrade to Angular CLI 1.5.

GitHub post: https://github.com/angular/angular-cli/issues/5526

answered Dec 14 '17 at 14:23

Ploutarchos Spyridonos

179
1
6

The given link might solve the issue. But if the link is revoked your answer turns useless. So please add a description. – Mathews Sunny Dec 14 '17 at 14:42

score 0 · Answer 4 · answered Jun 17 '20 at 13:30

0

Ensure that you don't have any unused imported member in your component. I was facing the same and I have removed the unused import and it's started working for me.

answered Jun 17 '20 at 13:30

Umair Khan

1

Branches on constructor not covered

4 Answers4

Linked