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

chore(e2e): bump protractor to 4.0.5 #2054

Merged
merged 1 commit into from
Sep 12, 2016

Conversation

cexbrayat
Copy link
Member

@cexbrayat cexbrayat commented Sep 11, 2016

Fixes #1977

Protractor 4.0.3 has a critical bug, and will return a success code even if the tests are failing or if there is no ng serve running... (see the related angular/protractor#3505)

4.0.5 fixes it, but it now relies on @types/node (as stated in the changelog https://github.com/angular/protractor/blob/master/CHANGELOG.md#405), which conflicts with the declarations in the typings.d.ts file. As they are now duplicated, removing them from the typings.d.ts file solves the problem.

declare var require: any; has to be added to the test.ts file because this is not the same NodeRequire that @types/node declares, but a WebpackRequire with the context field.

There is probably a more elegant solution to solve this, but at least this one unblocked us.

@hansl
Copy link
Contributor

hansl commented Sep 12, 2016

Wow, okay.

@hansl hansl merged commit a4fad1a into angular:master Sep 12, 2016
@hansl
Copy link
Contributor

hansl commented Sep 12, 2016

LGTM. Thanks!

filipesilva added a commit to filipesilva/angular-cli that referenced this pull request Sep 12, 2016
Followup from angular#2054

Now our files depend on the node typings, so we should have it as an explicit dependency.
hansl pushed a commit that referenced this pull request Sep 12, 2016
Followup from #2054

Now our files depend on the node typings, so we should have it as an explicit dependency.
@cexbrayat cexbrayat deleted the fix/1977-protractor branch September 12, 2016 06:02
@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 10, 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.

E2E Tests incorrect in default project
3 participants