Skip to content

chore: random test leaks #4380

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
May 4, 2017
Merged

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented May 3, 2017

Fixes some unit tests that were leaking elements into other tests.

Fixes some unit tests that were leaking elements into other tests.
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label May 3, 2017
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

Would be nice if we had something enforce that the page was pristine in-between specs, not sure how'd you do that.

@crisbeto
Copy link
Member Author

crisbeto commented May 3, 2017

AFAIK we could technically use a custom Jasmine reporter to run some logic after each test and check the DOM for leftovers (even though reporters aren't really meant to do this). I remember playing around with it for M1.

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker and removed pr: needs review labels May 3, 2017
@andrewseguin andrewseguin merged commit 7884b09 into angular:master May 4, 2017
@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 Sep 6, 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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants