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

Use protractor API for ng e2e #4415

Closed
filipesilva opened this issue Feb 3, 2017 · 2 comments
Closed

Use protractor API for ng e2e #4415

filipesilva opened this issue Feb 3, 2017 · 2 comments
Assignees
Labels
P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful

Comments

@filipesilva
Copy link
Contributor

We should be using the protractor API instead of running npm run protractor, similarly to #4248.

@filipesilva filipesilva added command: test P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful labels Feb 3, 2017
@filipesilva filipesilva self-assigned this Feb 3, 2017
@filipesilva
Copy link
Contributor Author

Dupe of #4256

@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 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful
Projects
None yet
Development

No branches or pull requests

1 participant