From dfffea9af36e56def401a44c05171a6324a365c8 Mon Sep 17 00:00:00 2001 From: Anton Andersen Date: Mon, 11 Aug 2014 12:39:47 +0400 Subject: [PATCH] Use config variables instead constants. Cleanup redundant constants --- apps/advanced/README.md | 4 +++- apps/advanced/backend/codeception.yml | 4 ++++ apps/advanced/backend/tests/_bootstrap.php | 13 ++++--------- apps/advanced/backend/tests/functional/_config.php | 4 ++-- apps/advanced/common/tests/_bootstrap.php | 9 --------- apps/advanced/console/tests/_bootstrap.php | 9 --------- apps/advanced/frontend/codeception.yml | 4 ++++ apps/advanced/frontend/tests/_bootstrap.php | 13 ++++--------- apps/advanced/frontend/tests/functional/_config.php | 4 ++-- 9 files changed, 23 insertions(+), 41 deletions(-) diff --git a/apps/advanced/README.md b/apps/advanced/README.md index b1d7351059..508a4140bd 100644 --- a/apps/advanced/README.md +++ b/apps/advanced/README.md @@ -113,7 +113,7 @@ it will upgrade your database to the last state according migrations. To be able to run acceptance tests you need a running webserver. For this you can use the php builtin server and run it in the directory where your main project folder is located. For example if your application is located in `/www/advanced` all you need to is: `cd /www` and then `php -S 127.0.0.1:8080` because the default configuration of acceptance tests expects the url of the application to be `/advanced/`. -If you already have a server configured or your application is not located in a folder called `advanced`, you may need to adjust the `TEST_ENTRY_URL` in `frontend/tests/_bootstrap.php` and `backend/tests/_bootstrap.php`. +If you already have a server configured or your application is not located in a folder called `advanced`, you may need to adjust the `test_entry_url` in `backend/codeception.yml` and `frontend/codeception.yml`. After that is done you should be able to run your tests, for example to run `frontend` tests do: @@ -123,5 +123,7 @@ After that is done you should be able to run your tests, for example to run `fro In similar way you can run tests for other application tiers - `backend`, `console`, `common`. +If you already have run `../vendor/bin/codecept build` for each application, you can run all tests by one command: `vendor/bin/codecept run` + You also can adjust you application suite configs and `_bootstrap.php` settings to use other urls and files, as it is can be done in `yii2-basic`. Current template also includes [yii2-faker](https://github.com/yiisoft/yii2/tree/master/extensions/faker) extension, that is correctly setup for each application tier. diff --git a/apps/advanced/backend/codeception.yml b/apps/advanced/backend/codeception.yml index b873ade13f..49a978b6dc 100644 --- a/apps/advanced/backend/codeception.yml +++ b/apps/advanced/backend/codeception.yml @@ -18,3 +18,7 @@ modules: user: '' password: '' dump: tests/_data/dump.sql +config: + # the entry script URL (without host info) for functional and acceptance tests + # PLEASE ADJUST IT TO THE ACTUAL ENTRY SCRIPT URL + test_entry_url: /advanced/backend/web/index-test.php diff --git a/apps/advanced/backend/tests/_bootstrap.php b/apps/advanced/backend/tests/_bootstrap.php index 76f6348cea..bc9d17c28a 100644 --- a/apps/advanced/backend/tests/_bootstrap.php +++ b/apps/advanced/backend/tests/_bootstrap.php @@ -1,12 +1,5 @@