feat(core): allow to provide multiple default testing modules #15054
Conversation
This can be used to e.g. add the NoopAnimationsModule by default: ``` TestBed.initTestEnvironment([ BrowserDynamicTestingModule, NoopAnimationsModule ], platformBrowserDynamicTesting()); ```
…r#15054) This can be used to e.g. add the NoopAnimationsModule by default: ``` TestBed.initTestEnvironment([ BrowserDynamicTestingModule, NoopAnimationsModule ], platformBrowserDynamicTesting()); ```
|
can you tell something about the performance effects when adding something in there as a module? I tried to use that like a testing default, but stuffed with all modules that appear very often in my tests (MaterialModule, FlexLayoutModule, ReactiveFormsModule...) to just import them in one central place and make my separate test files smaller. The test performance went down from 1:30 to over 5:00 min and it seems like Angular magic what is going on there because it's really only called once. Whereas importing a module with all singleton providers was a time gain. |
…r#15054) This can be used to e.g. add the NoopAnimationsModule by default: ``` TestBed.initTestEnvironment([ BrowserDynamicTestingModule, NoopAnimationsModule ], platformBrowserDynamicTesting()); ```
…r#15054) This can be used to e.g. add the NoopAnimationsModule by default: ``` TestBed.initTestEnvironment([ BrowserDynamicTestingModule, NoopAnimationsModule ], platformBrowserDynamicTesting()); ```
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
This can be used to e.g. add the NoopAnimationsModule by default: