deprecated Protractor helper (#3756)

Author: kobenguyent

.github/CONTRIBUTING.md

@@ -39,7 +39,7 @@ DEBUG=codeceptjs:* npx codeceptjs run
 
 ## Helpers
 
-Please keep in mind that CodeceptJS have **unified API** for Playwright, WebDriverIO, Appium, Protractor, Nightmare, Puppeteer, TestCafe. Tests written using those helpers should be compatible at syntax level. However, some of helpers may contain unique methods. That happens. If, for instance, WebDriverIO has method XXX and Nightmare doesn't, you can implement XXX inside Nightmare using the same method signature.
+Please keep in mind that CodeceptJS have **unified API** for Playwright, WebDriverIO, Appium, Nightmare, Puppeteer, TestCafe. Tests written using those helpers should be compatible at syntax level. However, some of helpers may contain unique methods. That happens. If, for instance, WebDriverIO has method XXX and Nightmare doesn't, you can implement XXX inside Nightmare using the same method signature.
 
 ### Updating Playwright | Puppeteer | WebDriver | Nightmare
 
@@ -187,8 +187,7 @@ docker-compose run --rm test-helpers test/rest
 
 #### Run acceptance tests
 
-To that we provide three separate services respectively for WebDriver, Nightmare, Puppeteer and
-Protractor tests:
+To that we provide three separate services respectively for WebDriver, Nightmare and Puppeteer tests:
 
 ```sh
 docker-compose run --rm test-acceptance.webdriverio

.github/PULL_REQUEST_TEMPLATE.md

@@ -10,7 +10,6 @@ Applicable helpers:
 - [ ] REST
 - [ ] FileHelper
 - [ ] Appium
-- [ ] Protractor
 - [ ] TestCafe
 - [ ] Playwright
 

README.md

@@ -36,7 +36,7 @@ CodeceptJS tests are:
 
 * **Synchronous**. You don't need to care about callbacks or promises or test scenarios which are linear. But, your tests should be linear.
 * Written from **user's perspective**. Every action is a method of `I`. That makes test easy to read, write and maintain even for non-tech persons.
-* Backend **API agnostic**. We don't know which WebDriver implementation is running this test. We can easily switch from WebDriverIO to Protractor or PhantomJS.
+* Backend **API agnostic**. We don't know which WebDriver implementation is running this test.
 
 CodeceptJS uses **Helper** modules to provide actions to `I` object. Currently, CodeceptJS has these helpers:
 
@@ -54,7 +54,7 @@ And more to come...
 
 CodeceptJS is a successor of [Codeception](http://codeception.com), a popular full-stack testing framework for PHP.
 With CodeceptJS your scenario-driven functional and acceptance tests will be as simple and clean as they can be.
-You don't need to worry about asynchronous nature of NodeJS or about various APIs of Selenium, Puppeteer, Protractor, TestCafe, etc. as CodeceptJS unifies them and makes them work as they are synchronous.
+You don't need to worry about asynchronous nature of NodeJS or about various APIs of Selenium, Puppeteer, TestCafe, etc. as CodeceptJS unifies them and makes them work as they are synchronous.
 
 
 ## Features

docs/custom-helpers.md

@@ -102,7 +102,7 @@ This way, if your tests are written with TypeScript, your IDE will be able to le
 
 ## Accessing Elements
 
-WebDriver, Puppeteer, Playwright, and Protractor drivers provide API for web elements.
+WebDriver, Puppeteer and Playwright drivers provide API for web elements.
 However, CodeceptJS do not expose them to tests by design, keeping test to be action focused.
 If you need to get access to web elements, it is recommended to implement operations for web elements in a custom helper.
 
@@ -154,7 +154,7 @@ You can also pass additional config options to your helper from a config - **(pl
 ```js
 helpers: {
   // here goes standard helpers:
-  // WebDriver, Protractor, Nightmare, etc...
+  // WebDriver, Nightmare, etc...
   // and their configuration
   MyHelper: {
     require: "./my_helper.js", // path to module

docs/data.md

@@ -23,7 +23,7 @@ API is supposed to be a stable interface and it can be used by acceptance tests.
 ## REST
 
 [REST helper](https://codecept.io/helpers/REST/) allows sending raw HTTP requests to application.
-This is a tool to make shortcuts and create your data pragmatically via API. However, it doesn't provide tools for testing APIs, so it should be paired with WebDriver, Nightmare or Protractor helpers for browser testing.
+This is a tool to make shortcuts and create your data pragmatically via API. However, it doesn't provide tools for testing APIs, so it should be paired with WebDriver helper for browser testing.
 
 Enable REST helper in the config. It is recommended to set `endpoint`, a base URL for all API requests. If you need some authorization you can optionally set default headers too.
 
@@ -92,7 +92,7 @@ I.sendPostRequest('/update-status', {}, { http_x_requested_with: 'xmlhttprequest
 ## GraphQL
 
 [GraphQL helper](https://codecept.io/helpers/GraphQL/) allows sending GraphQL queries and mutations to application, over Http.
-This is a tool to make shortcuts and create your data pragmatically via GraphQL endpoint. However, it doesn't provide tools for testing the endpoint, so it should be paired with WebDriver, Nightmare or Protractor helpers for browser testing.
+This is a tool to make shortcuts and create your data pragmatically via GraphQL endpoint. However, it doesn't provide tools for testing the endpoint, so it should be paired with WebDriver helpers for browser testing.
 
 Enable GraphQL helper in the config. It is recommended to set `endpoint`, the URL to which the requests go to. If you need some authorization you can optionally set default headers too.
 

docs/docker.md

@@ -56,7 +56,7 @@ services:
 
 ### Linking Containers
 
-If using the Protractor or WebDriver drivers, link the container with a Selenium Standalone docker container with an alias of `selenium`. Additionally, make sure your `codeceptjs.conf.js` contains the following to allow CodeceptJS to identify where Selenium is running.
+If using the WebDriver driver, link the container with a Selenium Standalone docker container with an alias of `selenium`. Additionally, make sure your `codeceptjs.conf.js` contains the following to allow CodeceptJS to identify where Selenium is running.
 
 ```javascript
   ...

docs/installation.md

@@ -59,7 +59,7 @@ For WebDriver installation Selenium Server is required 👇
 
 ## WebDriver
 
-WebDriver based helpers like WebDriver, Protractor, Selenium WebDriver will require [Selenium Server](https://codecept.io/helpers/WebDriver/#selenium-installation) installed. They will also require ChromeDriver or GeckoDriver to run corresponding browsers.
+WebDriver based helpers like WebDriver will require [Selenium Server](https://codecept.io/helpers/WebDriver/#selenium-installation) installed. They will also require ChromeDriver or GeckoDriver to run corresponding browsers.
 
 We recommend to install them manually or use NPM packages:
 

docs/mobile.md

@@ -123,7 +123,6 @@ Select [Appium helper](https://codecept.io/helpers/Appium/) when asked.
 ```sh
 ? What helpers do you want to use?
  ◯ WebDriver
- ◯ Protractor
  ◯ Puppeteer
  ◯ Nightmare
 ❯◉ Appium

docs/plugins.md

@@ -1152,8 +1152,6 @@ plugins: {
 }
 ```
 
-Please note, this service can be used with Protractor helper as well!
-
 #### Sauce Service
 
 Install `@wdio/sauce-service` package, as [described here][19].

docs/quickstart.md

@@ -31,7 +31,6 @@ TestCafe provides cross-browser support without Selenium. TestCafe tests are fas
 ---
 
 * [Mobile Testing with Appium »](/mobile)
-* [Testing with Protractor »](/angular)
 
 :::
 

docs/webdriver.md

@@ -21,8 +21,6 @@ Let's clarify the terms:
 
 We use [webdriverio](https://webdriver.io) library to run tests over WebDriver.
 
-> Popular tool [Protractor](/angular) also uses WebDriver for running end 2 end tests.
-
 To proceed you need to have [CodeceptJS installed](/quickstart#using-selenium-webdriver) and `WebDriver` helper selected.
 
 Selenium WebDriver may be complicated from start, as it requires following tools to be installed and started.