Dec 6, 2024
diff --git a/_includes/extensions.md b/_includes/extensions.md

 #### Installation

 Add this to the list of enabled extensions in `codeception.yml` or `acceptance.suite.yml`:
 Add this to the list of enabled extensions in `codeception.yml` or `Acceptance.suite.yml`:

 ``` yaml
 extensions:
 Can be configured in suite config:

 ```yaml
 #acceptance.suite.yml
 #Acceptance.suite.yml
 extensions:
    enabled:
        - Codeception\Extension\RunBefore:
 Can be configured in suite config:

 ```yaml
 #acceptance.suite.yml
 #Acceptance.suite.yml
 extensions:
    enabled:
        - Codeception\Extension\RunProcess:
 Multiple parameters can be passed as array:

 ```yaml
 #acceptance.suite.yml
 #Acceptance.suite.yml

 extensions:
    enabled:
diff --git a/docs/APITesting.md b/docs/APITesting.md

 The same way we tested a web site, Codeception allows you to test web services. They are very hard to test manually, so it's a really good idea to automate web service testing. We have SOAP and REST as standards, which are represented in corresponding modules, which we will cover in this chapter.

 You should start by creating a new test suite, (which was not provided by the `bootstrap` command). We recommend calling it **api** and using the `ApiTester` class for it.
 You should start by creating a new test suite, (which was not provided by the `bootstrap` command). We recommend calling it **Api** and using the `ApiTester` class for it.

 ```bash
 php vendor/bin/codecept generate:suiteapi
 php vendor/bin/codecept generate:suiteApi
 ```

 We will put all the api tests there.

 The REST web service is accessed via HTTP with standard methods: `GET`, `POST`, `PUT`, `DELETE`. They allow users to receive and manipulate entities from the service. Accessing a WebService requires an HTTP client, so for using it you need the module `PhpBrowser` or one of framework modules set up. For example, we can use the `Symfony` module for Symfony2 applications in order to ignore web server and test web service internally.

 Configure modules in `api.suite.yml`:
 Configure modules in `Api.suite.yml`:

 ```yaml
 actor: ApiTester
 Once we have configured our new testing suite, we can create the first sample test:

 ```bash
 php vendor/bin/codecept generate:cestapi CreateUser
 php vendor/bin/codecept generate:cestApi CreateUser
 ```

 It will be called `CreateUserCest.php`.

 ## Conclusion

 Codeception has two modules that will help you to test various web services. They need a new `api` suite to be created. Remember, you are not limited to test only response body. By including `Db` module you may check if a user has been created after the `CreateUser` call. You can improve testing scenarios by using REST or SOAP responses in your helper methods.
 Codeception has two modules that will help you to test various web services. They need a new `Api` suite to be created. Remember, you are not limited to test only response body. By including `Db` module you may check if a user has been created after the `CreateUser` call. You can improve testing scenarios by using REST or SOAP responses in your helper methods.


 <div class="alert alert-warning"><a href="https://github.com/Codeception/codeception.github.com/edit/master/docs/APITesting.md"><strong>Improve</strong> this guide</a></div>
diff --git a/docs/AcceptanceTests.md b/docs/AcceptanceTests.md
 We need to specify the `url` parameter in the acceptance suite config:

 ```yaml
 #acceptance.suite.yml
 #Acceptance.suite.yml
 actor: AcceptanceTester
 modules:
    enabled:
 We should start by creating a test with the next command:

 ```
 php vendor/bin/codecept g:cestacceptance Signin
 php vendor/bin/codecept g:cestAcceptance Signin
 ```

 It will be placed into `tests/acceptance` directory.
 It will be placed into `tests/Acceptance` directory.

 ```php
 class SigninCest

 Conditional assertions are disabled in bootstrap setup. To enable them you should add corresponding step decorators to suite config:

 > If you started project as `codecept initacceptance` they should be already enabled in config
 > If you started project as `codecept initAcceptance` they should be already enabled in config

 ```yaml
 # inacceptance.suite.yml
 # inAcceptance.suite.yml
 # or in codeception.yml inside suites section
 step_decorators:
  - \Codeception\Step\ConditionalAssertion

 To execute a test in a browser you need to change the suite configuration to use **WebDriver** module.

 Modify your `acceptance.suite.yml` file:
 Modify your `Acceptance.suite.yml` file:

 ```yaml
 actor: AcceptanceTester

 Retries are disabled by default. To enable them you should add retry step decorators to suite config:

 > If you started project as `codecept initacceptance` they should be already enabled in config
 > If you started project as `codecept initAcceptance` they should be already enabled in config

 ```yaml
 # inacceptance.suite.yml
 # inAcceptance.suite.yml
 # or in codeception.yml inside suites section
 step_decorators:
  - \Codeception\Step\Retry

 A/B testing is disabled by default. To enable it you should add corresponding step decorators to suite config:

 > If you started project as `codecept initacceptance` in Codeception >= 3.0 they should be already enabled in config
 > If you started project as `codecept initAcceptance` in Codeception >= 3.0 they should be already enabled in config

 ```yaml
 # inacceptance.suite.yml
 # inAcceptance.suite.yml
 # or in codeception.yml inside suites section
 step_decorators:
  - \Codeception\Step\TryTo
diff --git a/docs/AdvancedUsage.md b/docs/AdvancedUsage.md
 There are several ways to execute a bunch of tests. You can run tests from a specific directory:

 ```
 php vendor/bin/codecept run tests/acceptance/admin
 php vendor/bin/codecept run tests/Acceptance/admin
 ```

 You can execute one (or several) specific groups of tests:
diff --git a/docs/BDD.md b/docs/BDD.md
 We will assume that we will use scenarios in feature files for acceptance tests, so feature files to be placed in `acceptance` suite directory:

 ```bash
 php vendor/bin/codecept g:featureacceptance checkout
 php vendor/bin/codecept g:featureAcceptance checkout
 ```

 Generated template will look like this:
 We can test this scenario by executing it in dry-run mode. In this mode test won't be executed (actually, we didn't define any step for it, so it won't be executed in any case).

 ```bash
 php vendor/bin/codecept dry-runacceptance checkout.feature
 php vendor/bin/codecept dry-runAcceptance checkout.feature
 ```

 ```bash
 checkout: order several products
 Signature: checkout:order several products
 Test: tests/acceptance/checkout.feature:order several products
 Test: tests/Acceptance/checkout.feature:order several products
 Scenario --
 In order to buy product
 As a customer
 We can define them easily by executing `gherkin:snippets` command for the given suite:

 ```bash
 php vendor/bin/codecept gherkin:snippetsacceptance
 php vendor/bin/codecept gherkin:snippetsAcceptance
 ```

 This will produce code templates for all undefined steps in all feature files of this suite.
 If you decided to run your features with Codeception, we recommend to start with symlinking your `features` directory into one of the test suites:

 ```bash
 ln -s $PWD/features tests/acceptance
 ln -s $PWD/features tests/Acceptance
 ```

 Then you will need to implement all step definitions. Run `gherkin:snippets` to generate stubs for them.
diff --git a/docs/Codecoverage.md b/docs/Codecoverage.md
 ### Remote Server

 But if you run tests on different server (or your webserver doesn't use code from current directory) a single option `remote` should be added to config.
 For example, let's turn on remote coverage for acceptance suite in `acceptance.suite.yml`:
 For example, let's turn on remote coverage for acceptance suite in `Acceptance.suite.yml`:


 ```yaml
diff --git a/docs/ContinuousIntegration.md b/docs/ContinuousIntegration.md
 # Test
 test:
  script:
    - vendor/bin/codecept runacceptance --xml --html
    - vendor/bin/codecept runAcceptance --xml --html
  artifacts:
    when: always
    expire_in: 1 week
diff --git a/docs/Customization.md b/docs/Customization.md
 If you want to run a specific suite from the application you can execute:

 ```bash
 php vendor/bin/codecept rununit -c frontend
 php vendor/bin/codecept runUnit -c frontend
 ```

 Where `unit` is the name of suite and the `-c` option specifies the path to the `codeception.yml` configuration file to use.
 Where `Unit` is the name of suite and the `-c` option specifies the path to the `codeception.yml` configuration file to use.
 In this example we will assume that there is `frontend/codeception.yml` configuration file
 and that we will execute the unit tests for only that app.


 ```

 Extensions can also be enabled per suite inside suite configs (like `acceptance.suite.yml`) and for a specific environment.
 Extensions can also be enabled per suite inside suite configs (like `Acceptance.suite.yml`) and for a specific environment.

 To enable extension dynamically, execute the `run` command with `--ext` option.
 Provide a class name as a parameter:
 ```
 php vendor/bin/codecept run -c ~/projects/ecommerce/
 php vendor/bin/codecept run -c ~/projects/drupal
 php vendor/bin/codecept generate:cestacceptance CreateArticle -c ~/projects/drupal/
 php vendor/bin/codecept generate:cestAcceptance CreateArticle -c ~/projects/drupal/

 ```

 ```yaml
 groups:
  # add 2 tests to db group
  db: [tests/unit/PersistTest.php, tests/unit/DataTest.php]
  db: [tests/Unit/PersistTest.php, tests/Unit/DataTest.php]

  # add all tests from a directory to api group
  api: [tests/functional/api]
  api: [tests/Functional/api]

 ```

 A list of tests for the group can be passed from a Group file. It should be defined in plain text with test names on separate lines:

 ```
 tests/unit/DbTest.php
 tests/unit/UserTest.php:creat
 tests/unit/UserTest.php:update
 tests/Unit/DbTest.php
 tests/Unit/UserTest.php:creat
 tests/Unit/UserTest.php:update

 ```
 A group file can be included by its relative filename:
 It is possible to run specific suites from included applications:

 * `codecept run` ⬅ Execute all tests from all apps and all suites
 * `codecept rununit` ⬅ Runs unit suite from the current app
 * `codecept run admin::unit` ⬅ Runs unit suite from admin app
 * `codecept run *::unit` ⬅ Runs unit suites from all included apps and NOT the root suite
 * `codecept rununit,*::unit` ⬅ Runs included unit suites AND root unit suite
 * `codecept runfunctional,*::unit` ⬅ Runs included unit suites and root functional suite
 * `codecept runUnit` ⬅ Runs unit suite from the current app
 * `codecept run admin::Unit` ⬅ Runs unit suite from admin app
 * `codecept run *::Unit` ⬅ Runs unit suites from all included apps and NOT the root suite
 * `codecept runUnit,*::Unit` ⬅ Runs included unit suites AND root unit suite
 * `codecept runFunctional,*::Unit` ⬅ Runs included unit suites and root functional suite


 <div class="alert alert-warning"><a href="https://github.com/Codeception/codeception.github.com/edit/master/docs/Customization.md"><strong>Improve</strong> this guide</a></div>
diff --git a/docs/ParallelExecution.md b/docs/ParallelExecution.md


 ```bash
 tests/functional/LoginCept.php
 tests/functional/AdminCest.php:createUser
 tests/functional/AdminCest.php:deleteUser
 tests/Functional/LoginCept.php
 tests/Functional/AdminCest.php:createUser
 tests/Functional/AdminCest.php:deleteUser
 ```

 Tasks from `\Codeception\Task\SplitTestsByGroups` will generate non-intersecting group files.  You can either split your tests by files or by single tests:
    // Split your tests by files
    $this->taskSplitTestFilesByGroups(5)
        ->projectRoot('.')
        ->testsFrom('tests/acceptance')
        ->testsFrom('tests/Acceptance')
        ->groupsTo('tests/Support/Data/paracept_')
        ->run();

    /*
    // Split your tests by single tests (alternatively)
    $this->taskSplitTestsByGroups(5)
        ->projectRoot('.')
        ->testsFrom('tests/acceptance')
        ->testsFrom('tests/Acceptance')
        ->groupsTo('tests/Support/Data/paracept_')
        ->run();
    */


 ```bash
 php vendor/bin/codecept runacceptance -g paracept_2
 php vendor/bin/codecept runAcceptance -g paracept_2
 ```

 #### Step 2: Running Tests
    for ($i = 1; $i <= 5; $i++) {
        $parallel->process(
            $this->taskCodecept() // use built-in Codecept task
            ->suite('acceptance') // run acceptance tests
            ->suite('Acceptance') // run acceptance tests
            ->group("paracept_$i") // for all paracept_* groups
            ->xml("tests/_log/result_$i.xml") // save XML results
        );
diff --git a/docs/ReusingTestCode.md b/docs/ReusingTestCode.md
 Codeception can generate a PageObject class for you with command:

 ```
 php vendor/bin/codecept generate:pageobjectacceptance Login
 php vendor/bin/codecept generate:pageobjectAcceptance Login
 ```

 > It is recommended to use page objects for acceptance testing only
 Lets create an Admin StepObject with the generator:

 ```
 php vendor/bin/codecept generate:stepobjectacceptance Admin
 php vendor/bin/codecept generate:stepobjectAcceptance Admin
 ```

 You can supply optional action names. Enter one at a time, followed by a newline.
 End with an empty line to continue to StepObject creation.

 ```
 php vendor/bin/codecept generate:stepobjectacceptance Admin
 php vendor/bin/codecept generate:stepobjectAcceptance Admin
 Add action to StepObject class (ENTER to exit): loginAsAdmin
 Add action to StepObject class (ENTER to exit):
 StepObject was created in /tests/acceptance/_support/Step/Acceptance/Admin.php
 StepObject was created in /tests/Acceptance/_support/Step/Acceptance/Admin.php
 ```

 This will generate a class in `/tests/Support/Step/Acceptance/Admin.php` similar to this:
diff --git a/docs/UnitTests.md b/docs/UnitTests.md
 php vendor/bin/codecept generate:test Unit Example
 ```

 It creates a new `ExampleTest` file located in the `tests/unit` directory.
 It creates a new `ExampleTest` file located in the `tests/Unit` directory.

 As always, you can run the newly created test with this command:

 ```

 To enable the database functionality in unit tests, make sure the `Db` module is included
 in the `unit.suite.yml` configuration file.
 in the `Unit.suite.yml` configuration file.
 The database will be cleaned and populated after each test, the same way it happens for acceptance and functional tests.
 If that's not your required behavior, change the settings of the `Db` module for the current suite. See [Db Module](https://codeception.com/docs/modules/Db)

diff --git a/docs/modules/Apc.md b/docs/modules/Apc.md
 * Stability: **stable**
 * Contact: serghei@phalcon.io

 #### Example (`unit.suite.yml`)
 #### Example (`Unit.suite.yml`)

 {% highlight yaml %}
Original file line number	Diff line number	Diff line change
Expand Up		@@ -75,7 +75,7 @@ The screenshots are saved to `tests/_output/record_*` directories, open `index.h

		#### Installation

		Add this to the list of enabled extensions in `codeception.yml` or `acceptance.suite.yml`:
		Add this to the list of enabled extensions in `codeception.yml` or `Acceptance.suite.yml`:

		``` yaml
		extensions:
Expand DownExpand Up		@@ -136,7 +136,7 @@ Dependent processes run sequentially one by one.
		Can be configured in suite config:

		```yaml
		#acceptance.suite.yml
		#Acceptance.suite.yml
		extensions:
		enabled:
		- Codeception\Extension\RunBefore:
Expand DownExpand Up		@@ -193,7 +193,7 @@ Can be used to start/stop selenium server, chromedriver, mailcatcher, etc.
		Can be configured in suite config:

		```yaml
		#acceptance.suite.yml
		#Acceptance.suite.yml
		extensions:
		enabled:
		- Codeception\Extension\RunProcess:
Expand All		@@ -203,7 +203,7 @@ extensions:
		Multiple parameters can be passed as array:

		```yaml
		#acceptance.suite.yml
		#Acceptance.suite.yml

		extensions:
		enabled:
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -9,10 +9,10 @@ title: API Testing - Codeception Docs

		The same way we tested a web site, Codeception allows you to test web services. They are very hard to test manually, so it's a really good idea to automate web service testing. We have SOAP and REST as standards, which are represented in corresponding modules, which we will cover in this chapter.

		You should start by creating a new test suite, (which was not provided by the `bootstrap` command). We recommend calling it api and using the `ApiTester` class for it.
		You should start by creating a new test suite, (which was not provided by the `bootstrap` command). We recommend calling it Api and using the `ApiTester` class for it.

		```bash
		php vendor/bin/codecept generate:suiteapi
		php vendor/bin/codecept generate:suiteApi
		```

		We will put all the api tests there.
Expand All		@@ -23,7 +23,7 @@ We will put all the api tests there.

		The REST web service is accessed via HTTP with standard methods: `GET`, `POST`, `PUT`, `DELETE`. They allow users to receive and manipulate entities from the service. Accessing a WebService requires an HTTP client, so for using it you need the module `PhpBrowser` or one of framework modules set up. For example, we can use the `Symfony` module for Symfony2 applications in order to ignore web server and test web service internally.

		Configure modules in `api.suite.yml`:
		Configure modules in `Api.suite.yml`:

		```yaml
		actor: ApiTester
Expand DownExpand Up		@@ -60,7 +60,7 @@ modules:
		Once we have configured our new testing suite, we can create the first sample test:

		```bash
		php vendor/bin/codecept generate:cestapi CreateUser
		php vendor/bin/codecept generate:cestApi CreateUser
		```

		It will be called `CreateUserCest.php`.
Expand DownExpand Up		@@ -379,7 +379,7 @@ class Api extends \Codeception\Module {

		## Conclusion

		Codeception has two modules that will help you to test various web services. They need a new `api` suite to be created. Remember, you are not limited to test only response body. By including `Db` module you may check if a user has been created after the `CreateUser` call. You can improve testing scenarios by using REST or SOAP responses in your helper methods.
		Codeception has two modules that will help you to test various web services. They need a new `Api` suite to be created. Remember, you are not limited to test only response body. By including `Db` module you may check if a user has been created after the `CreateUser` call. You can improve testing scenarios by using REST or SOAP responses in your helper methods.


		<div class="alert alert-warning"><a href="https://github.com/Codeception/codeception.github.com/edit/master/docs/APITesting.md"><strong>Improve</strong> this guide</a></div>
Original file line number	Diff line number	Diff line change
Expand Up		@@ -57,7 +57,7 @@ Common PhpBrowser drawbacks:
		We need to specify the `url` parameter in the acceptance suite config:

		```yaml
		#acceptance.suite.yml
		#Acceptance.suite.yml
		actor: AcceptanceTester
		modules:
		enabled:
Expand All		@@ -68,10 +68,10 @@ modules:
		We should start by creating a test with the next command:

		```
		php vendor/bin/codecept g:cestacceptance Signin
		php vendor/bin/codecept g:cestAcceptance Signin
		```

		It will be placed into `tests/acceptance` directory.
		It will be placed into `tests/Acceptance` directory.

		```php
		class SigninCest
Expand DownExpand Up		@@ -268,10 +268,10 @@ Each failed assertion will be shown in the test results, but it won't stop the t

		Conditional assertions are disabled in bootstrap setup. To enable them you should add corresponding step decorators to suite config:

		> If you started project as `codecept initacceptance` they should be already enabled in config
		> If you started project as `codecept initAcceptance` they should be already enabled in config

		```yaml
		# inacceptance.suite.yml
		# inAcceptance.suite.yml
		# or in codeception.yml inside suites section
		step_decorators:
		- \Codeception\Step\ConditionalAssertion
Expand DownExpand Up		@@ -390,7 +390,7 @@ Now, you are ready to run WebDriver tests using Codeception.

		To execute a test in a browser you need to change the suite configuration to use WebDriver module.

		Modify your `acceptance.suite.yml` file:
		Modify your `Acceptance.suite.yml` file:

		```yaml
		actor: AcceptanceTester
Expand DownExpand Up		@@ -503,10 +503,10 @@ $I->retry(4, 400);

		Retries are disabled by default. To enable them you should add retry step decorators to suite config:

		> If you started project as `codecept initacceptance` they should be already enabled in config
		> If you started project as `codecept initAcceptance` they should be already enabled in config

		```yaml
		# inacceptance.suite.yml
		# inAcceptance.suite.yml
		# or in codeception.yml inside suites section
		step_decorators:
		- \Codeception\Step\Retry
Expand DownExpand Up		@@ -578,10 +578,10 @@ if ($I->tryToSeeElement('.alert')) {

		A/B testing is disabled by default. To enable it you should add corresponding step decorators to suite config:

		> If you started project as `codecept initacceptance` in Codeception >= 3.0 they should be already enabled in config
		> If you started project as `codecept initAcceptance` in Codeception >= 3.0 they should be already enabled in config

		```yaml
		# inacceptance.suite.yml
		# inAcceptance.suite.yml
		# or in codeception.yml inside suites section
		step_decorators:
		- \Codeception\Step\TryTo
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -192,7 +192,7 @@ public function testNotReadyToday()
		There are several ways to execute a bunch of tests. You can run tests from a specific directory:

		```
		php vendor/bin/codecept run tests/acceptance/admin
		php vendor/bin/codecept run tests/Acceptance/admin
		```

		You can execute one (or several) specific groups of tests:
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -88,7 +88,7 @@ Feature file is written in Gherkin format. Codeception can generate a feature fi
		We will assume that we will use scenarios in feature files for acceptance tests, so feature files to be placed in `acceptance` suite directory:

		```bash
		php vendor/bin/codecept g:featureacceptance checkout
		php vendor/bin/codecept g:featureAcceptance checkout
		```

		Generated template will look like this:
Expand DownExpand Up		@@ -151,13 +151,13 @@ And in the end we are verifying our expectation using Then keyword. The acti
		We can test this scenario by executing it in dry-run mode. In this mode test won't be executed (actually, we didn't define any step for it, so it won't be executed in any case).

		```bash
		php vendor/bin/codecept dry-runacceptance checkout.feature
		php vendor/bin/codecept dry-runAcceptance checkout.feature
		```

		```bash
		checkout: order several products
		Signature: checkout:order several products
		Test: tests/acceptance/checkout.feature:order several products
		Test: tests/Acceptance/checkout.feature:order several products
		Scenario --
		In order to buy product
		As a customer
Expand All		@@ -181,7 +181,7 @@ Besides the scenario steps listed we got the notification that our steps are not
		We can define them easily by executing `gherkin:snippets` command for the given suite:

		```bash
		php vendor/bin/codecept gherkin:snippetsacceptance
		php vendor/bin/codecept gherkin:snippetsAcceptance
		```

		This will produce code templates for all undefined steps in all feature files of this suite.
Expand DownExpand Up		@@ -551,7 +551,7 @@ While Behat is a great tool for Behavior Driven Development, you still may prefe
		If you decided to run your features with Codeception, we recommend to start with symlinking your `features` directory into one of the test suites:

		```bash
		ln -s $PWD/features tests/acceptance
		ln -s $PWD/features tests/Acceptance
		```

		Then you will need to implement all step definitions. Run `gherkin:snippets` to generate stubs for them.
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -153,7 +153,7 @@ coverage:
		### Remote Server

		But if you run tests on different server (or your webserver doesn't use code from current directory) a single option `remote` should be added to config.
		For example, let's turn on remote coverage for acceptance suite in `acceptance.suite.yml`:
		For example, let's turn on remote coverage for acceptance suite in `Acceptance.suite.yml`:


		```yaml
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -181,7 +181,7 @@ before_script:
		# Test
		test:
		script:
		- vendor/bin/codecept runacceptance --xml --html
		- vendor/bin/codecept runAcceptance --xml --html
		artifacts:
		when: always
		expire_in: 1 week
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -35,10 +35,10 @@ and you want to get a single report in JUnit and HTML format. The code coverage
		If you want to run a specific suite from the application you can execute:

		```bash
		php vendor/bin/codecept rununit -c frontend
		php vendor/bin/codecept runUnit -c frontend
		```

		Where `unit` is the name of suite and the `-c` option specifies the path to the `codeception.yml` configuration file to use.
		Where `Unit` is the name of suite and the `-c` option specifies the path to the `codeception.yml` configuration file to use.
		In this example we will assume that there is `frontend/codeception.yml` configuration file
		and that we will execute the unit tests for only that app.

Expand DownExpand Up		@@ -199,7 +199,7 @@ extensions:

		```

		Extensions can also be enabled per suite inside suite configs (like `acceptance.suite.yml`) and for a specific environment.
		Extensions can also be enabled per suite inside suite configs (like `Acceptance.suite.yml`) and for a specific environment.

		To enable extension dynamically, execute the `run` command with `--ext` option.
		Provide a class name as a parameter:
Expand DownExpand Up		@@ -371,7 +371,7 @@ You can pass the `-c` option to any Codeception command (except `bootstrap`), to
		```
		php vendor/bin/codecept run -c ~/projects/ecommerce/
		php vendor/bin/codecept run -c ~/projects/drupal
		php vendor/bin/codecept generate:cestacceptance CreateArticle -c ~/projects/drupal/
		php vendor/bin/codecept generate:cestAcceptance CreateArticle -c ~/projects/drupal/

		```

Expand All		@@ -393,19 +393,19 @@ Tests for groups can be specified as an array of file names or directories conta
		```yaml
		groups:
		# add 2 tests to db group
		db: [tests/unit/PersistTest.php, tests/unit/DataTest.php]
		db: [tests/Unit/PersistTest.php, tests/Unit/DataTest.php]

		# add all tests from a directory to api group
		api: [tests/functional/api]
		api: [tests/Functional/api]

		```

		A list of tests for the group can be passed from a Group file. It should be defined in plain text with test names on separate lines:

		```
		tests/unit/DbTest.php
		tests/unit/UserTest.php:creat
		tests/unit/UserTest.php:update
		tests/Unit/DbTest.php
		tests/Unit/UserTest.php:creat
		tests/Unit/UserTest.php:update

		```
		A group file can be included by its relative filename:
Expand DownExpand Up		@@ -542,11 +542,11 @@ You should also specify the path to the `log` directory, where the reports and l
		It is possible to run specific suites from included applications:

		* `codecept run` ⬅ Execute all tests from all apps and all suites
		* `codecept rununit` ⬅ Runs unit suite from the current app
		* `codecept run admin::unit` ⬅ Runs unit suite from admin app
		* `codecept run *::unit` ⬅ Runs unit suites from all included apps and NOT the root suite
		* `codecept rununit,*::unit` ⬅ Runs included unit suites AND root unit suite
		* `codecept runfunctional,*::unit` ⬅ Runs included unit suites and root functional suite
		* `codecept runUnit` ⬅ Runs unit suite from the current app
		* `codecept run admin::Unit` ⬅ Runs unit suite from admin app
		* `codecept run *::Unit` ⬅ Runs unit suites from all included apps and NOT the root suite
		* `codecept runUnit,*::Unit` ⬅ Runs included unit suites AND root unit suite
		* `codecept runFunctional,*::Unit` ⬅ Runs included unit suites and root functional suite


		<div class="alert alert-warning"><a href="https://github.com/Codeception/codeception.github.com/edit/master/docs/Customization.md"><strong>Improve</strong> this guide</a></div>
Original file line number	Diff line number	Diff line change
Expand Up		@@ -146,9 +146,9 @@ Codeception can organize tests into [groups](https://codeception.com/docs/Advanc


		```bash
		tests/functional/LoginCept.php
		tests/functional/AdminCest.php:createUser
		tests/functional/AdminCest.php:deleteUser
		tests/Functional/LoginCept.php
		tests/Functional/AdminCest.php:createUser
		tests/Functional/AdminCest.php:deleteUser
		```

		Tasks from `\Codeception\Task\SplitTestsByGroups` will generate non-intersecting group files. You can either split your tests by files or by single tests:
Expand All		@@ -159,15 +159,15 @@ public function parallelSplitTests()
		// Split your tests by files
		$this->taskSplitTestFilesByGroups(5)
		->projectRoot('.')
		->testsFrom('tests/acceptance')
		->testsFrom('tests/Acceptance')
		->groupsTo('tests/Support/Data/paracept_')
		->run();

		/*
		// Split your tests by single tests (alternatively)
		$this->taskSplitTestsByGroups(5)
		->projectRoot('.')
		->testsFrom('tests/acceptance')
		->testsFrom('tests/Acceptance')
		->groupsTo('tests/Support/Data/paracept_')
		->run();
		*/
Expand DownExpand Up		@@ -207,7 +207,7 @@ Let's try to execute tests from the second group:


		```bash
		php vendor/bin/codecept runacceptance -g paracept_2
		php vendor/bin/codecept runAcceptance -g paracept_2
		```

		#### Step 2: Running Tests
Expand All		@@ -228,7 +228,7 @@ public function parallelRun()
		for ($i = 1; $i <= 5; $i++) {
		$parallel->process(
		$this->taskCodecept() // use built-in Codecept task
		->suite('acceptance') // run acceptance tests
		->suite('Acceptance') // run acceptance tests
		->group("paracept_$i") // for all paracept_* groups
		->xml("tests/_log/result_$i.xml") // save XML results
		);
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -95,7 +95,7 @@ Do not hard-code complex CSS or XPath locators in your tests but rather move the
		Codeception can generate a PageObject class for you with command:

		```
		php vendor/bin/codecept generate:pageobjectacceptance Login
		php vendor/bin/codecept generate:pageobjectAcceptance Login
		```

		> It is recommended to use page objects for acceptance testing only
Expand DownExpand Up		@@ -197,17 +197,17 @@ We call such a classes StepObjects.
		Lets create an Admin StepObject with the generator:

		```
		php vendor/bin/codecept generate:stepobjectacceptance Admin
		php vendor/bin/codecept generate:stepobjectAcceptance Admin
		```

		You can supply optional action names. Enter one at a time, followed by a newline.
		End with an empty line to continue to StepObject creation.

		```
		php vendor/bin/codecept generate:stepobjectacceptance Admin
		php vendor/bin/codecept generate:stepobjectAcceptance Admin
		Add action to StepObject class (ENTER to exit): loginAsAdmin
		Add action to StepObject class (ENTER to exit):
		StepObject was created in /tests/acceptance/_support/Step/Acceptance/Admin.php
		StepObject was created in /tests/Acceptance/_support/Step/Acceptance/Admin.php
		```

		This will generate a class in `/tests/Support/Step/Acceptance/Admin.php` similar to this:
Expand Down