@@ -90,7 +90,7 @@ Enable Laravel module in `unit.suite.yml` to have its methods inside a testcase.
### Acceptance Tests
-To test an application in a real environment by using its UI you should use a real browser. Codeception uses Selenium Webdriver and corresponding WebDriver module to interact with a browser. You should configure `acceptance.suite.yml` to use WebDriver module and a browser of your choice.
+To test an application in a real environment by using its UI you should use a real browser. Codeception uses Selenium Webdriver and corresponding WebDriver module to interact with a browser. You should configure `Acceptance.suite.yml` to use WebDriver module and a browser of your choice.
```yaml
class_name: AcceptanceTester
@@ -157,13 +157,13 @@ Laravel module actions like `amOnPage` or `see` should not be available for test
### BDD
-If you prefer to describe application with feature files, Codeception can turn them to acceptance or functional tests. It is recommended to store feature files in `features` directory (like it does Behat) but symlinking it to `tests/acceptance/features` or `tests/functional/features` so they can be treated as tests too. For using BDD with acceptance tests you need to run:
+If you prefer to describe application with feature files, Codeception can turn them to acceptance or functional tests. It is recommended to store feature files in `features` directory (like it does Behat) but symlinking it to `tests/Acceptance/features` or `tests/Functional/features` so they can be treated as tests too. For using BDD with acceptance tests you need to run:
```
-ln -s $PWD/features tests/acceptance
+ln -s $PWD/features tests/Acceptance
```
-Codeception allows to combine tests written in different formats. If are about to wirite a regression test it probably should not be described as a product's feature. That's why feature-files is subset of all acceptance tests, and they are stored in subfolder of `tests/acceptance`.
+Codeception allows to combine tests written in different formats. If are about to wirite a regression test it probably should not be described as a product's feature. That's why feature-files is subset of all acceptance tests, and they are stored in subfolder of `tests/Acceptance`.
There is no standard Gherkin steps built in. By writing your feature files you can get code snippets which should be added to `AcceptanceTester` class.
diff --git a/for/phalcon.md b/for/phalcon.md
index 875036c48..2be2084c4 100644
--- a/for/phalcon.md
+++ b/for/phalcon.md
@@ -36,7 +36,7 @@ This will create `tests` directory and configuration file `codeception.yml`. Thi
### Unit Testing
-Add Phalcon to your unit test by adding the following to your `unit.suite.yml`:
+Add Phalcon to your unit test by adding the following to your `Unit.suite.yml`:
```yaml
# Codeception Test Suite Configuration
#
@@ -57,7 +57,7 @@ modules:
To generate a plain PHPUnit test for class `Users`, run:
```
-vendor/bin/codecept g:test unit Users
+vendor/bin/codecept g:test Unit Users
```
Actions of the Phalcon module will be accessible from `$this->tester` inside a test of `Codeception\Test\Unit`.
@@ -95,7 +95,7 @@ modules:
Then use [Cest](https://codeception.com/docs/07-AdvancedUsage) or Cept to create a test.
```
-vendor/bin/codecept g:cest functional Login
+vendor/bin/codecept g:cest Functional Login
```
Then add your test case
```php
@@ -138,7 +138,7 @@ class LoginCest
### Acceptance Testing
-Sample configuration of `tests/acceptance.suite.yml`:
+Sample configuration of `tests/Acceptance.suite.yml`:
```yaml
class_name: AcceptanceTester
@@ -155,10 +155,10 @@ Browser can be specified as `chrome`, `firefox`, `phantomjs`, or others.
To create a sample test called, run:
```
-vendor/bin/codecept g:cest acceptance Login
+vendor/bin/codecept g:cest Acceptance Login
```
-This will create the file `tests/acceptance/LoginCest.php`. Each method of a class (except `_before` and `_after`) is a test. Tests use `$I` object (instance of `AcceptanceTester` class) to perform actions on a webpage. Methods of `AcceptanceTester` are proxified to corresponding modules, which in current case is `WebDriver`.
+This will create the file `tests/Acceptance/LoginCest.php`. Each method of a class (except `_before` and `_after`) is a test. Tests use `$I` object (instance of `AcceptanceTester` class) to perform actions on a webpage. Methods of `AcceptanceTester` are proxified to corresponding modules, which in current case is `WebDriver`.
@@ -168,7 +168,7 @@ This will create the file `tests/acceptance/LoginCest.php`. Each method of a cla
To run the tests you will need chrome browser, [selenium server running](https://codeception.com/docs/modules/WebDriver#Selenium). If this requirements met acceptance tests can be executed as
```
-vendor/bin/codecept run acceptance
+vendor/bin/codecept run Acceptance
```
### BDD
@@ -176,7 +176,7 @@ vendor/bin/codecept run acceptance
If you prefer to describe application with feature files, Codeception can turn them to acceptance tests. It is recommended to store feature files in `features` directory (like Behat does it) but symlinking it to `tests/acceptance/features` so they can be treated as tests too.
```
-ln -s $PWD/features tests/acceptance
+ln -s $PWD/features tests/Acceptance
```
Codeception allows to combine tests written in different formats. If you are about to write a regression test it probably should not be described as a product's feature. That's why feature-files are a subset of all acceptance tests, and they are stored in subfolder of `tests/acceptance`.
diff --git a/for/yii.md b/for/yii.md
index 293078b7f..592e369e2 100644
--- a/for/yii.md
+++ b/for/yii.md
@@ -35,7 +35,7 @@ Run them by executing in terminal:
### Unit Tests
-Unit tests are located in `tests/unit` directory and are supposed to contain all kind of unit and integration testing.
+Unit tests are located in `tests/Unit` directory and are supposed to contain all kind of unit and integration testing.
Each test case extends `Codeception\Test\Unit` class, which is standard Codeception format for unit testing.
It is pretty hard to develop completely isolated unit tests in Yii, so an application is bootstrapped before each test case. Tests are configured in `tests/unit.suite.yml` file with Yii2 module enabled:
@@ -152,10 +152,10 @@ Yii2 module actions like `amOnPage` or `see` should not be available for testing
From a test perspective acceptance tests do the same as functional tests. They test the user interaction with application but in this case using *real* browser and web server. They are much slower and much more fragile. They should not duplicate functional tests in matter of testing functionality but should be used for testing the UI of your application. If you are unsure which tests should be acceptance and which are functional, write acceptance tests for JavaScript-rich applications, where UI highly depends on a browser processing. You can also use acceptance tests for happy-path scenarios, just to ensure that a real user using a real browser achieve the same results you expect in functional tests.
-By default in basic application acceptance tests are disabled (as they require web server, Selenium Server and browser to be running). You can easily enable them by renaming `acceptance.suite.yml.example` to `acceptance.suite.yml`
+By default in basic application acceptance tests are disabled (as they require web server, Selenium Server and browser to be running). You can easily enable them by renaming `Acceptance.suite.yml.example` to `Acceptance.suite.yml`
```
-mv tests/acceptance.suite.yml.example tests/acceptance.suite.yml
+mv tests/Acceptance.suite.yml.example tests/Acceptance.suite.yml
```
Basic template uses `codeception/base` package which doesn't contain `facebook/webdriver` library required to run acceptance tests. Please change `codeception/base` to `codeception/codeception` in `composer.json` and run the update command.
@@ -169,7 +169,7 @@ Then you will need to launch application server in test mode:
and start a [Selenium Server](https://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
+# config at tests/Acceptance.yml
modules:
enabled:
- WebDriver:
@@ -186,7 +186,7 @@ As it was said, functional and acceptance tests are similar, so in order to avoi
Similar as for functional tests it is recommended to use Cest format for acceptance testing:
```
-./vendor/bin/codecept g:cest acceptance MyNewScenarioCest
+./vendor/bin/codecept g:cest Acceptance MyNewScenarioCest
```
@@ -222,10 +222,10 @@ Create basic test suites
./vendor/bin/codecept bootstrap
```
-Enable module Yii2 for functional tests inside `functional.suite.yml`:
+Enable module Yii2 for functional tests inside `Functional.suite.yml`:
```yml
-# functional.suite.yml
+# Functional.suite.yml
modules:
enabled:
- Yii2:
+ src="https://poser.pugx.org/codeception/codeception/downloads.png"
+ alt="Total Downloads">