do not use composer exec for running codeception

it produces weird behavior.

fixes #104
This commit is contained in:
Carsten Brandt 2017-02-01 11:29:32 +01:00
parent b3e97d7940
commit 9035c63988
No known key found for this signature in database
GPG Key ID: BE4F41DE1DEEEED0
2 changed files with 8 additions and 8 deletions

View File

@ -26,4 +26,4 @@ install:
script:
- |
php -S localhost:8080 -t web > /dev/null 2>&1 &
composer exec codecept run
vendor/bin/codecept run

View File

@ -116,7 +116,7 @@ By default there are 3 test suites:
Tests can be executed by running
```
composer exec codecept run
vendor/bin/codecept run
```
The command above will execute unit and functional tests. Unit tests are testing the system components, while functional
@ -164,13 +164,13 @@ To execute acceptance tests do the following:
```
# run all available tests
composer exec codecept run
vendor/bin/codecept run
# run acceptance tests
composer exec codecept run acceptance
vendor/bin/codecept run acceptance
# run only unit and functional tests
composer exec codecept run unit,functional
vendor/bin/codecept run unit,functional
```
### Code coverage support
@ -180,13 +180,13 @@ to collect code coverage. You can run your tests and collect coverage with the f
```
#collect coverage for all tests
composer exec codecept run -- --coverage-html --coverage-xml
vendor/bin/codecept run -- --coverage-html --coverage-xml
#collect coverage only for unit tests
composer exec codecept run unit -- --coverage-html --coverage-xml
vendor/bin/codecept run unit -- --coverage-html --coverage-xml
#collect coverage for unit and functional tests
composer exec codecept run functional,unit -- --coverage-html --coverage-xml
vendor/bin/codecept run functional,unit -- --coverage-html --coverage-xml
```
You can see code coverage output under the `tests/_output` directory.