Skip to content

Commit 20914b6

Browse files
committed
docs(tutorial): mention that Protractor might need upgrading
Since Protractor requires specific WebDriver versions and these are only compatible with specific browser version ranges, it is often necessary to upgrade Protractor just so that it picks up a more recent WebDriver version. Related: angular#16739
1 parent d5feee8 commit 20914b6

File tree

1 file changed

+12
-0
lines changed

1 file changed

+12
-0
lines changed

docs/content/tutorial/index.ngdoc

+12
Original file line numberDiff line numberDiff line change
@@ -281,6 +281,18 @@ It is good to run the E2E tests whenever you make changes to the HTML views or w
281281
the application as a whole is executing correctly. It is very common to run E2E tests before pushing
282282
a new commit of changes to a remote repository.
283283

284+
<div class="alert alert-warning">
285+
<p>
286+
Each version of Protractor is compatible with specific browser versions. If you are reading this
287+
some time in the future, it is possible that the specified Protractor version is no longer
288+
compatible with the latest version of Chrome that you are using.
289+
</p>
290+
<p>
291+
If that is the case, you can try upgrading Protractor to newer version. For instructions on how
292+
to upgrade dependencies see [Updating dependencies](tutorial/#updating-dependencies).
293+
</p>
294+
</div>
295+
284296

285297
### Updating dependencies
286298

0 commit comments

Comments
 (0)