Skip to content

build: setup default browser for running legacy tests locally #20620

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

devversion
Copy link
Member

Sometimes the legacy Karma tests might fail and one might want
to debug those. Currently the Gulp task can be run for that, but
it's not starting any browser so one needs to launch Chrome manually.

Tests usually fail then because the browser has different dimensions
but our test expectations rely on a specific dimension. i.e. 1024x768

Sometimes the legacy Karma tests might fail and one might want
to debug those. Currently the Gulp task can be run for that, but
it's not starting any browser so one needs to launch Chrome manually.

Tests usually fail then because the browser has different dimensions
but our test expectations rely on a specific dimension. i.e. 1024x768
@devversion devversion added merge safe target: patch This PR is targeted for the next patch release labels Sep 21, 2020
@devversion devversion requested a review from a team as a code owner September 21, 2020 21:04
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Sep 21, 2020
Copy link
Member

@crisbeto crisbeto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Sep 22, 2020
@annieyw annieyw merged commit e8265cc into angular:master Sep 22, 2020
annieyw pushed a commit that referenced this pull request Sep 22, 2020
Sometimes the legacy Karma tests might fail and one might want
to debug those. Currently the Gulp task can be run for that, but
it's not starting any browser so one needs to launch Chrome manually.

Tests usually fail then because the browser has different dimensions
but our test expectations rely on a specific dimension. i.e. 1024x768

(cherry picked from commit e8265cc)
@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 Oct 23, 2020
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 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