Remove PhantomJS from ParallelExecution and framework pages

ThomasLandauer · web-flow · commit e5d0312781cc · 2020-11-23T08:30:19.000+02:00
* Update 12-ParallelExecution.md Removing PhantomJS, see Codeception/module-webdriver#28 (comment) * Update symfony.md * Update laravel.md * Update yii.md * Update 07-AdvancedUsage.md
diff --git a/docs/07-AdvancedUsage.md b/docs/07-AdvancedUsage.md
@@ -384,13 +384,6 @@ modules:
             url: 'http://127.0.0.1:8000/'
             browser: 'firefox'
 
-env:
-    phantom:
-         modules:
-            config:
-                WebDriver:
-                    browser: 'phantomjs'
-
     chrome:
          modules:
             config:
@@ -402,7 +395,7 @@ env:
 
 {% endhighlight %}
 
-Basically you can define different environments inside the `env` root, name them (`phantom`, `chrome` etc.),
+Basically you can define different environments inside the `env` root, name them (`chrome`, `firefox` etc.),
 and then redefine any configuration parameters that were set before.
 
 You can also define environments in separate configuration files placed in the directory specified by the `envs` option in
@@ -439,19 +432,19 @@ modules:
 The environment configuration files are merged into the main configuration before the suite configuration is merged.
 
 You can easily switch between those configs by running tests with `--env` option.
-To run the tests only for PhantomJS you just need to pass `--env phantom` as an option:
+To run the tests only for Firefox you just need to pass `--env firefox` as an option:
 
 {% highlight bash %}
 
-$ php vendor/bin/codecept run acceptance --env phantom
+$ php vendor/bin/codecept run acceptance --env firefox
 
 {% endhighlight %}
 
-To run the tests in all 3 browsers, list all the environments:
+To run the tests in all browsers, list all the environments:
 
 {% highlight bash %}
 
-$ php vendor/bin/codecept run acceptance --env phantom --env chrome --env firefox
+$ php vendor/bin/codecept run acceptance --env chrome --env firefox
 
 {% endhighlight %}
 
@@ -461,7 +454,7 @@ It's also possible to merge multiple environments into a single configuration by
 
 {% highlight bash %}
 
-$ php vendor/bin/codecept run acceptance --env dev,phantom --env dev,chrome --env dev,firefox
+$ php vendor/bin/codecept run acceptance --env dev,firefox --env dev,chrome --env dev,firefox
 
 {% endhighlight %}
 
@@ -479,10 +472,10 @@ The desired environments can be specified with the `@env` annotation for tests i
 class UserCest
 {
     /**
-     * This test will be executed only in 'firefox' and 'phantom' environments
+     * This test will be executed only in 'firefox' and 'chrome' environments
      *
      * @env firefox
-     * @env phantom
+     * @env chrome
      */
     public function webkitOnlyTest(AcceptanceTester $I)
     {
@@ -498,7 +491,7 @@ For Cept you should use simple comments:
 
 <?php
 // @env firefox
-// @env phantom
+// @env chrome
 
 {% endhighlight %}
 
@@ -540,9 +533,8 @@ while in Cest you should retrieve it through dependency injection:
 <?php
 public function myTest(\AcceptanceTester $I, \Codeception\Scenario $scenario)
 {
-    if ($scenario->current('browser') == 'phantomjs') {
-      // emulate popups for PhantomJS
-      $I->executeScript('window.alert = function(){return true;}');
+    if ($scenario->current('browser') == 'chrome') {
+      // ...
     }
 }
 
diff --git a/docs/12-ParallelExecution.md b/docs/12-ParallelExecution.md
@@ -5,7 +5,7 @@ title: 12-ParallelExecution - Codeception - Documentation
 
 # Parallel Execution
 
-When execution time of your tests is longer than a coffee break, it is a good reason to think about making your tests faster. If you have already tried to run them on SSD drive, or to use PhantomJS instead of Selenium, and the execution time still upsets you, it might be a good idea to run your tests in parallel.
+When execution time of your tests is longer than a coffee break, it is a good reason to think about making your tests faster. If you have already tried to run them on SSD drive, and the execution time still upsets you, it might be a good idea to run your tests in parallel.
 
 ## Where to start
 
@@ -472,4 +472,4 @@ Codeception does not provide tools for parallel test execution. This is a comple
 
 
 
-* **Previous Chapter: [< ContinuousIntegration](/docs/12-ContinuousIntegration)**
+* **Previous Chapter: [< ContinuousIntegration](/docs/12-ContinuousIntegration)**
diff --git a/for/laravel.md b/for/laravel.md
@@ -101,7 +101,7 @@ modules:
         - \Helper\Acceptance            
 ```
 
-Browser can be specified as `firefox`, `chrome`, `phantomjs`, or others. 
+Browser can be specified as `firefox`, `chrome`, or others. 
 
 Acceptance tests will be executed in development environment using real web server, so settings from `.env.testing` can't be passed to them. 
 
diff --git a/for/symfony.md b/for/symfony.md
@@ -47,7 +47,7 @@ modules:
         - \Helper\Acceptance            
 ```
 
-Browser can be specified as `chrome`, `firefox`, `phantomjs`, or others. 
+Browser can be specified as `chrome`, `firefox`, or others. 
 
 To create a sample test called, run:
 
diff --git a/for/yii.md b/for/yii.md
@@ -166,7 +166,7 @@ Then you will need to launch application server in test mode:
 ./tests/bin/yii serve
 ```
 
-and start a [Selenium Server or PhantomJS](http://codeception.com/docs/modules/WebDriver#Local-Testing). For acceptance WebDriver module is used. Please check its reference to learn how to work with it. Unlike Yii2 module it does know nothing about your application, so if you want to use features of Yii like fixtures for acceptance testing, you should check that enable Yii2 module is enabled as well:
+and start a [Selenium Server](http://codeception.com/docs/modules/WebDriver#Local-Testing). For acceptance WebDriver module is used. Please check its reference to learn how to work with it. Unlike Yii2 module it does know nothing about your application, so if you want to use features of Yii like fixtures for acceptance testing, you should check that enable Yii2 module is enabled as well:
 
 ```yml
 # config at tests/acceptance.yml
