Angular Unit Testing - Is there an advantage to calling ngOnDestroy() or fixture.destroy()?

Viewed 387

I have seen the practice of manually destroying the component in afterEach() with something like the following:

afterEach() {
  component.ngOnDestroy();
  // or fixture.destroy();
}

Is there a performance enhancement in doing this? I couldn't see in the documentation any concern for destroying a component after each unit test. Does it speed up a large batch of unit tests running? Are there memory leaks otherwise while other tests continue to run? Is there a difference for jest vs jasmine+karma?

0 Answers
Related