Remove testing dependencies from application templates

[samdark]

Currently basic application has the following in dependencies:

"yiisoft/yii2-codeception": "*",
"codeception/codeception": "*",
"codeception/specify": "*",
"codeception/verify": "*",

It triggers pretty big download and isn't actually needed in lots of cases where the application is to be used.

I propose removing it from dependencies and instead putting it to readme.

Doing that we still need to keep tests running on travis.

[Ragazzo]

I am ok with this, but as for me i got my yii2-basic less then a minute, so it is more of internet provider settings.

[samdark]

Well, another issue is that you need 512 MB of RAM to install it.

[Ragazzo]

not sure, could be so maybe, i have not measured this, on my pc i have 16GB, so such problems for me are just skiped. but as i said i am ok with this.

[qiangxue]

• We should keep yiisoft/yii2-codeception in the dependency as it's very small.
• We may then update tests/README.md and include instructions on how to install codecept via either phar or composer.
• .travis.yml needs to be updated to install codeception.

[samdark]

Why keeping yiisoft/yii2-codeception if it cannot work without codeception itself?

[Ragazzo]

Why keeping yiisoft/yii2-codeception if it cannot work without codeception itself?

it can, you can download phar or install via composer.

@qiangxue also note that we are using specify/verify that are not included in phar.

[samdark]

Makes sense.

[qiangxue]

also note that we are using specify/verify that are not included in phar.

Perhaps we should suggest @davert to include them in phar? Right now they depend on PHPUnit package. If they are required via composer, it means PHPUnit package will be installed while codeception phar already includes PHPUnit.

[Ragazzo]

@qiangxue he is DavertMik ;) yes, we can, but i am not sure if it is a good way, @DavertMik want to exclude all unneeded dependencies from Codeception. But worth trying to ask :)

[DavertMik]

Ok, I agree pretty much testing dependencies for basic application. Especially when not too many developers will be interested in testing from start.

Right now I work on codeception 2.0 which goes to master branch (as unstable development). I'm trying to do less BC breaks when possible, and last night I got everything back green on Travis, but still I should apologize for any issues that may happen, as you rely on the master branch. I promise to stabilize it before the Yii2 RC released.

specify can't be included into codecept.phar for 1.8 version, because in 1.8 Codeception requires PHP 5.3. But I was planning to it into 2.0 as it needs be 5.4. I think verify will be added as well.

Right now there is no phar package for Codeception 2.0. I'm going to build it when I have first release.

Also you may put codeception dependencies into the suggests section.

[yupe]

I think that we should include Codeception into yii2-codeception extension. In my project yii2-codeception is in "require-dev" section of composer.json and we also can install project with "--no-dev" option.

[Ragazzo]

Section suggest has wrong format, also add docs to README.md under tests directory that first step should be php composer.phar require --dev "codeception/codeception: 1.8.*@dev" "codeception/specify: *" "codeception/verify: *"

[samdark]

All fixed.