chore(e2e): bump protractor to 4.0.5 #2054
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 thetypings.d.ts
file. As they are now duplicated, removing them from thetypings.d.ts
file solves the problem.declare var require: any;
has to be added to thetest.ts
file because this is not the sameNodeRequire
that@types/node
declares, but aWebpackRequire
with thecontext
field.There is probably a more elegant solution to solve this, but at least this one unblocked us.