Skip to content
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

test(sidenav): refactor flaky tests in Edge #16625

Merged
merged 1 commit into from
Aug 1, 2019

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Jul 27, 2019

Refactors some tests to (hopefully) be less flaky in Edge. In two of them I've replaced calls to getComputedStyle to a check against a class in the DOM. On other one I've changed the assertions for IE and Edge to something that is less accurate, but also less likely to flake.

@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jul 27, 2019
Refactors some tests to (hopefully) be less flaky in Edge. In two of them I've replaced calls to `getComputedStyle` to a check against a class in the DOM. On other one I've changed the assertions for IE and Edge to something that is less accurate, but also less likely to flake.
@crisbeto crisbeto force-pushed the sidenav-flaky-tests branch from 4db68f6 to b85dd24 Compare July 27, 2019 10:30
@crisbeto crisbeto added P2 The issue is important to a large percentage of users, with a workaround pr: merge safe target: patch This PR is targeted for the next patch release labels Jul 27, 2019
@crisbeto crisbeto marked this pull request as ready for review July 27, 2019 11:06
@crisbeto crisbeto requested a review from mmalerba as a code owner July 27, 2019 11:06
@mmalerba mmalerba added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Jul 27, 2019
@jelbourn jelbourn merged commit 8e321ae into angular:master Aug 1, 2019
mmalerba pushed a commit that referenced this pull request Aug 14, 2019
Refactors some tests to (hopefully) be less flaky in Edge. In two of them I've replaced calls to `getComputedStyle` to a check against a class in the DOM. On other one I've changed the assertions for IE and Edge to something that is less accurate, but also less likely to flake.

(cherry picked from commit 8e321ae)
@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 11, 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 P2 The issue is important to a large percentage of users, with a workaround 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