diff options
| author | Preston Marshall | 2013-10-25 06:40:02 -0500 |
|---|---|---|
| committer | Pete Bacon Darwin | 2013-10-26 19:50:43 +0100 |
| commit | 8b7473856867a8507ac5e833410d316fdf1b3177 (patch) | |
| tree | dd21f9f041baa9aafcc4f61e7b3bd69f4b1a29f4 | |
| parent | 96da4c14a79b5d053a079ed0e2486ed29d0e9e43 (diff) | |
| download | angular.js-8b7473856867a8507ac5e833410d316fdf1b3177.tar.bz2 | |
docs(guide/e2e-testing): add note about Protractor replacement
Add a note to warn people starting new projects about Protractor replacing the
current ngScenario way of doing E2E testing.
Closes #4644
| -rw-r--r-- | docs/content/guide/dev_guide.e2e-testing.ngdoc | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/docs/content/guide/dev_guide.e2e-testing.ngdoc b/docs/content/guide/dev_guide.e2e-testing.ngdoc index 080d7307..d0481512 100644 --- a/docs/content/guide/dev_guide.e2e-testing.ngdoc +++ b/docs/content/guide/dev_guide.e2e-testing.ngdoc @@ -3,6 +3,10 @@ @name Developer Guide: E2E Testing @description +**If you're starting a new Angular project, you may want to look into +using {@link https://github.com/angular/protractor Protractor}, as it is going to +replace the currrent method of E2E Testing in the near future.** + As applications grow in size and complexity, it becomes unrealistic to rely on manual testing to verify the correctness of new features, catch bugs and notice regressions. |