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

build: run edge tests on browserstack #20662

Merged
merged 1 commit into from Sep 29, 2020

Conversation

@crisbeto
Copy link
Member

@crisbeto crisbeto commented Sep 27, 2020

Moves the Edge tests to Browserstack to avoid the recent issues with Saucelabs.

@googlebot googlebot added the cla: yes label Sep 27, 2020
@crisbeto crisbeto force-pushed the crisbeto:karma-launchers-update branch 2 times, most recently from 940398a to 37ba1c0 Sep 27, 2020
@crisbeto crisbeto closed this Sep 27, 2020
@crisbeto crisbeto reopened this Sep 27, 2020
@crisbeto crisbeto force-pushed the crisbeto:karma-launchers-update branch 9 times, most recently from 55aa082 to 0f60f4c Sep 27, 2020
Moves the Edge tests to Browserstack to avoid the recent issues with Saucelabs.
@crisbeto crisbeto force-pushed the crisbeto:karma-launchers-update branch from 0f60f4c to 78b6d8d Sep 27, 2020
@crisbeto crisbeto changed the title build: update karma dependencies build: run edge tests on browserstack Sep 27, 2020
@crisbeto crisbeto marked this pull request as ready for review Sep 27, 2020
@crisbeto crisbeto requested review from devversion, mmalerba and angular/dev-infra-components as code owners Sep 27, 2020
@@ -354,23 +354,23 @@ export function crossEnvironmentSpecs(
});

it('should be able to hover', async () => {
const host = await harness.host();
let classAttr = await host.getAttribute('class');
const box = await harness.hoverTest();

This comment has been minimized.

@crisbeto

crisbeto Sep 27, 2020
Author Member

I decided to change these tests to hover an element inside the host, instead of the host itself, because the first assertion, that ensures that the element doesn't start off as hovered, was breaking on Browserstack. What I think was going on is that it would put the cursor inside the viewport when the window is opened, throwing off our assertion since the host takes up most of the screen and the cursor would land on it.

Copy link
Member

@josephperrott josephperrott left a comment

LGTM

Copy link
Member

@jelbourn jelbourn left a comment

LGTM

@mmalerba mmalerba merged commit 8b6aab1 into angular:master Sep 29, 2020
16 checks passed
16 checks passed
Inclusive Language Check completed with success
Details
ci/angular: merge status All checks passed!
ci/circleci: api_golden_checks Your tests passed on CircleCI!
Details
ci/circleci: bazel_build Your tests passed on CircleCI!
Details
ci/circleci: build_release_packages Your tests passed on CircleCI!
Details
ci/circleci: e2e_tests Your tests passed on CircleCI!
Details
ci/circleci: integration_tests Your tests passed on CircleCI!
Details
ci/circleci: lint Your tests passed on CircleCI!
Details
ci/circleci: ngcc_compatibility Your tests passed on CircleCI!
Details
ci/circleci: tests_browserstack Your tests passed on CircleCI!
Details
ci/circleci: tests_local_browsers Your tests passed on CircleCI!
Details
ci/circleci: tests_saucelabs Your tests passed on CircleCI!
Details
ci/circleci: upload_release_packages Your tests passed on CircleCI!
Details
ci/circleci: view_engine_build Your tests passed on CircleCI!
Details
ci/circleci: view_engine_test Your tests passed on CircleCI!
Details
cla/google All necessary CLAs are signed
mmalerba added a commit that referenced this pull request Sep 29, 2020
Moves the Edge tests to Browserstack to avoid the recent issues with Saucelabs.

(cherry picked from commit 8b6aab1)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

6 participants
You can’t perform that action at this time.