You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: for/yii.md
+5-5Lines changed: 5 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ Once you created a project from a [basic template](https://github.com/yiisoft/yi
27
27
Run them by executing in terminal:
28
28
29
29
```
30
-
composer exec codecept run
30
+
./vendor/bin/codecept run
31
31
```
32
32
33
33

@@ -109,7 +109,7 @@ Codeception provides standard set of actions like `amOnPage`, `submitForm`, `see
109
109
Functional tests should be written inside [Cest files](http://codeception.com/docs/07-AdvancedUsage#Cest-Classes), which is a scenario-driven test format of Codeception. You can easily create a new test by running:
API tests are not included in any Yii templates so you need to set up them manually if you developing a web service. API testing is done at functional testing level but instead of testing HTML responses on user actions, they test requests and responses via protocols like REST or SOAP. To start writing api tests you should create a suite for them
124
124
125
125
```
126
-
composer exec codecept g:suite api
126
+
./vendor/bin/codecept g:suite api
127
127
```
128
128
129
129
You will need to enable `REST`, `Yii2` module in `tests/api.suite.yml`:
@@ -186,7 +186,7 @@ As it was said, functional and acceptance tests are similar, so in order to avoi
186
186
Similar as for functional tests it is recommended to use Cest format for acceptance testing:
0 commit comments