-
Notifications
You must be signed in to change notification settings - Fork 6.8k
test(select): switch all select tests to fakeAsync #7913
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly LGTM, seems like there's still a failure on Edge.
|
||
it('should set the role of the select to listbox', () => { | ||
it('should set the role of the select to listbox', fakeAsync(() => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Most of these tests aren't doing anything async, why do we have to bring them into the fakeAsync
zone (aside from consistency)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just added it to everything for safety. Some of the tests that weren't marked as async actually were and could leak async operations into later tests. I figured this way we guarantee that won't happen
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, apply the merge ready label when the Edge issue is sorted out.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
ab6c605
to
62033f7
Compare
No idea whats up with that one test. Verified that it looks correct when visiting the demo site on Edge. I opted to just not run the test on Edge (which is still better than prior to this PR where the test wasn't actually run on any browser due to a bug). |
Needs rebase |
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. |
No description provided.