Update the guide per latest release

lucatume · web-flow · commit 55c704c69dae · 2017-06-05T18:30:51.000+02:00
diff --git a/for/wordpress.md b/for/wordpress.md
@@ -42,21 +42,20 @@ WPBrowser will install the latest version of Codeception for you.
 ## Setup
 
 To fully use the WordPress specific modules of the WPBrowser suite you need to setup a local WordPress installation; this is in no way different from what's required to locally develop a WordPress theme or plugin.  
-In the examples below I assume that the local WordPress installation root directory is `/var/www/wordpress`, that it responds at the `http://wordpress.dev` URL and that I am developing a plugin called "Acme Plugin".  
-While it's possible to start from a default Codeception configuration the WPBrowser package comes with its own CLI tool (`wpcept`) and its own bootstrap command.  
-Scaffold the tests using the latter
+In the examples below I assume that the local WordPress installation root directory is `/var/www/wordpress`, that it responds at the `http://wordpress.localhost` URL and that I am developing a plugin called "Acme Plugin".  
+While it's possible to start from a default Codeception configuration the WPBrowser package comes with its own initialization template that can be called using:
 
 ```bash
-wpcept bootstrap
+codecept init wpbrowser
 ```
 
-The command creates the `tests` directory and scaffold the `acceptance`, `functional`, `integration` and `unit` suites creating a `tests` sub-directory and a configuration file for each.  
-Edit the `codeception.yml` file to match your local WordPress setup and point the modules to the local WordPress installation folder, the local WordPress URL and so on.  
+The command offers the possibility to scaffold an empty suite or to undergo an interactive setup that will end in a ready to run Codeception for WordPress installation; it will create the `tests` directory and scaffold the `acceptance`, `functional`, `wpunit` and `unit` suites creating a `tests` sub-directory and a configuration file for each.  
+If you did not use the step-by-step initialization then edit each suite configuration file (e.g. `tests/functional.suite.yml` for the functional suite) to match your local WordPress setup and point the modules to the local WordPress installation folder, the local WordPress URL and so on.  
 If you are using the `WPLoader` module in your tests take care to create a dedicated database for it and not to use the same database the `Db` or `WPDb` modules might use.  
 The use of the modules defined in the WPBrowser package is not tied to this bootstrap though so feel free to set up Codeception in any other way.
 
 ## Integration Tests
-Commonly "WordPress unit tests" are not related to classical unit tests but to integration tests. The difference is that unit tests are supposed to test a class methods in complete isolation, while integration tests check how components work inside WordPress. That's why, to prepare WordPress for testing, you should enable `WPLoader` module into `integration.suite.yml`.  
+Commonly "WordPress unit tests" (hence the `wpunit` default name of the suite) are not related to classical unit tests but to integration tests. The difference is that unit tests are supposed to test a class methods in complete isolation, while integration tests check how components work inside WordPress. That's why, to prepare WordPress for testing, you should enable `WPLoader` module into `wpunit.suite.yml`.  
 The `WPLoader` module: it takes care of loading, installing and configuring a fresh WordPress installation before each test method runs.  
 To handle the heavy lifting the module requires some information about the local WordPress installation: in the `codeception.yml` file configure it to match your local setup; with reference to the example above the module configuration might be:
 
@@ -71,17 +70,17 @@ modules:
             dbPassword: root
             wpDebug: true
             tablePrefix: wptests_
-            domain: wordpress.dev
+            domain:wordpress.localhost 
             plugins:
                 - acme-plugin/plugin.php
             activatePlugins:
                 - acme-plugin/plugin.php
 ```
 
-The module is wrapping and augmenting the [WordPress Core automated testing suite](https://make.wordpress.org/core/handbook/testing/automated-testing/phpunit/) and to generate a test case that uses Codeception and the methods provided by the Core testing suite you can use the `wpcept` command again:
+The module is wrapping and augmenting the [WordPress Core automated testing suite](https://make.wordpress.org/core/handbook/testing/automated-testing/phpunit/) and to generate a test case that uses Codeception and the methods provided by the Core testing suite you can use the generation command provided by the package:
 
 ```bash
-wpcept generate:wpunit integration "Acme\SomeClass"
+codecept generate:wpunit integration "Acme\SomeClass"
 ```
 
 The generated test case extends the `WPTestCase` class and it exposes all the mehtods defined by `Codeception\Test\Unit` test case and the Core suite `\WP_UnitTestCase`.  
@@ -96,27 +95,29 @@ Any database interaction is wrapped in a transaction to guarantee isolation betw
 
 ## WordPress Functional Tests
 Functional tests are meant to test requests handling and end-to-end interactions.  
-WPBrowser will scaffold functional tests to use the `WPBrowser`, `WPDb` and `Filesystem` modules.  
-While the latter is the one defined by the Codeception suite `WPBrowser` and `WPDb` modules extend the Codeception `PHPBrowser` and `Db` modules with WordPress specific methods.  
+WPBrowser will scaffold functional tests to use the `WordPress`, `WPDb` and `Filesystem` modules.  
+While the latter is the one defined by the Codeception suite `WordPress` and `WPDb` modules extend the Codeception framework and `Db` modules with WordPress specific methods.  
 The modules will require some WordPress specific setup parameters:
 
 ```yaml
 modules:
     enabled:
-        WPBrowser:
-            url: 'http://wordpress.dev'
-            adminUsername: admin
-            adminPassword: password
-            adminUrl: /wp-admin
+        - Filesystem 
         WPDb:
             dsn: 'mysql:host=localhost;dbname=wordpress'
             user: root
             password: root
             dump: tests/_data/wp.sql
             populate: true
             cleanup: true
-            url: 'http://wordpress.dev'
+            url: 'http://wordpress.localhost'
             tablePrefix: wp_
+        WordPress:
+            depends: WPDb
+            wpRootFolder: /var/www/wordpress
+            adminUsername: admin
+            adminPassword: password
+            adminPath: /wp-admin
 ```
 
 To generate a functional test use the default `codecept` commmand.
@@ -141,7 +142,7 @@ The modules require some WordPress specific parameters to work:
 modules:
     enabled:
         WPWebDriver:
-            url: 'http://wordpress.dev'
+            url: 'http://wordpress.localhost'
             browser: phantomjs
             port: 4444
             restart: true
