fix(core): move TestBed TestingModule reset to afterEach #21737
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Currently the
TestingModule
is reset usingbeforeEach
, resetting the module before each test is run. This prevents code that manages destruction of Modules, Components, Services, etc. from being able to properly destroy.Issue Number: #18831
What is the new behavior?
The
TestingModule
is reset usingafterEach
, ensuring that the destruction of the all pieces get a change to properly clean up.Does this PR introduce a breaking change?
Tests which are broken by this change are likely revealing leaks within their code because of improper tear downs occurring before this change.
Other information