Skip to content

test(material-experimental): harness tests leaking overlay containers #17007

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 9, 2019

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Sep 8, 2019

Fixes the cdk-overlay-container nodes not being cleaned up between test harness tests.

Fixes the `cdk-overlay-container` nodes not being cleaned up between test harness tests.
@crisbeto crisbeto added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent pr: merge safe target: patch This PR is targeted for the next patch release labels Sep 8, 2019
@crisbeto crisbeto requested a review from devversion as a code owner September 8, 2019 12:13
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Sep 8, 2019
Copy link
Member

@devversion devversion left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I recently made a change in the dialog harness tests to clear out the dialogs, but I guess the idea is to also remove the actual empty overlay container right?

@crisbeto
Copy link
Member Author

crisbeto commented Sep 8, 2019

Yeah the container is still there. Currently there will always be one, because we have some logic that clears all other containers, but once #17006 lands we'll leak one container per test.

@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Sep 8, 2019
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Related: now that we're going to have /testing paths for our subpackages, I'm considering adding something like CdkTestingModule and MatTestingModule that would ideally do things like clean up these elements in an afterEach

@jelbourn jelbourn merged commit 4a5e952 into angular:master Sep 9, 2019
crisbeto added a commit to crisbeto/material2 that referenced this pull request Sep 9, 2019
Fixes a failure that wasn't caught by the CI in angular#17007 for some reason. We were only injecting the overlay container for one kind of test harness.
jelbourn pushed a commit that referenced this pull request Sep 9, 2019
Fixes a failure that wasn't caught by the CI in #17007 for some reason. We were only injecting the overlay container for one kind of test harness.
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Oct 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants