Skip to content

test(material/menu): switch all tests to fakeAsync #23203

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
Jul 23, 2021

Conversation

crisbeto
Copy link
Member

We were only using fakeAsync on about half of the menu tests which could cause state to leak between them. These changes add fakeAsync to all of them to try and address the recent flakes that we've been seeing.

@google-cla google-cla bot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jul 20, 2021
@crisbeto crisbeto marked this pull request as ready for review July 20, 2021 21:08
@crisbeto crisbeto added merge safe 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 labels Jul 20, 2021
@crisbeto crisbeto requested a review from jelbourn July 20, 2021 21:08
@crisbeto crisbeto force-pushed the menu-async-tests branch 3 times, most recently from 00027c2 to bd48a54 Compare July 21, 2021 08:29
We were only using `fakeAsync` on about half of the menu tests which could cause state to leak between them. These changes add `fakeAsync` to all of them to try and address the recent flakes that we've been seeing.
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

@jelbourn jelbourn added the action: merge The PR is ready for merge by the caretaker label Jul 21, 2021
@mmalerba mmalerba merged commit 24c35a4 into angular:master Jul 23, 2021
@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 Aug 23, 2021
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.

4 participants