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

feat(e2e): use protractor api #4527

Merged
merged 2 commits into from
Feb 9, 2017
Merged

Conversation

filipesilva
Copy link
Contributor

@filipesilva filipesilva commented Feb 8, 2017

Uses existing Protractor API to run it directly instead of using npm run e2e.

Also adds support for the following flags: --serve, --config,
--specs, --element-explorer, --webdriver-update.

Fix #4256
Fix #4478
Close #1054

BREAKING CHANGE: ng e2e no longer needs ng serve to be running.

@filipesilva filipesilva requested review from hansl and Brocco February 8, 2017 14:57
@filipesilva filipesilva force-pushed the use-protractor-api branch 3 times, most recently from e8b2066 to ab02a2e Compare February 8, 2017 19:45
@hansl
Copy link
Contributor

hansl commented Feb 9, 2017

@vikerman Please review this from the protractor side :)

if (e2eTaskOptions.webdriverUpdate) {
// webdriver-manager can only be accessed via a deep import from within
// protractor/node_modules. A double deep import if you will.
const webdriverUpdate = requireProjectModule(projectRoot,
Copy link
Contributor

@vikerman vikerman Feb 9, 2017

Choose a reason for hiding this comment

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

This should be ok for now - This interface is not changing for now. Will see how we can make this public for the future.

Uses existing Protractor API to run it directly instead of using `npm run
e2e`.

Also adds support for the following flags: `--serve`, `--config`,
`--specs`, `--element-explorer`, `--webdriver-update`.

Fix angular#4256
Fix angular#4478

BREAKING CHANGE: `ng e2e` no longer needs `ng serve` to be running.
@hansl hansl merged commit 8d2d93a into angular:master Feb 9, 2017
@filipesilva filipesilva deleted the use-protractor-api branch February 9, 2017 23:20
asnowwolf pushed a commit to asnowwolf/angular-cli that referenced this pull request Apr 12, 2017
Uses existing Protractor API to run it directly instead of using `npm run
e2e`.

Also adds support for the following flags: `--serve`, `--config`,
`--specs`, `--element-explorer`, `--webdriver-update`.

Fix angular#4256
Fix angular#4478

BREAKING CHANGE: `ng e2e` no longer needs `ng serve` to be running.
@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
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Flakey-ness in e2e tests with ng serve Use protractor api instead of npm run e2e in ng e2e
4 participants