modified tests, improved configuration, introduced aspect

[Ragazzo]

I improved current testing support by adding AspectMock and Specify. What benefits we get:

1. AspectMock allows us to mock directly to the class. Great ability. Can be compared to mockery but it uses class aliases and can cause fatal error when same name class will be included.
2. Specify syntax sugar that adds good readability. Also it is a best practice to structure in blocks your assertions, so they will be easy to read and understand.

This two repos are maintained by @DavertMik so we will get support from him i think. Also you can review and see by yourself that tests are easy to use/read/understand.

I made some _bootstrap.php modifications because of AspectMock should be initialized before Yii, and load it internally.

[Ragazzo]

@qiangxue i do really think that this changes should be implemented because of they are very useful for developers especially who are starting to learn TDD for example.

[Ragazzo]

Related with this issue #1709 and this one #1694 as example of how it can help developer to mock things.

[qiangxue]

AspectMock should be initialized before Yii, and load it internally.

Why?

[Ragazzo]

It is Go! AOP framework (created by @lisachenko) limitation, generally it is because of how AOP work. Some links:

• http://codeception.com/09-13-2013/understanding-aspectmock.html
• http://codeception.com/10-04-2013/specification-phpunit.html

[Ragazzo]

I think we also can wait @DavertMik as a creator of AspectMock for bringing up some internal knowledges.

[DavertMik]

I'd rather leave AspectMock aside. Sure it is really effective tool especially for unit testing in Yii and the only option in such cases as form testing here goes a link to my post on that.

But I'd rather not introduce this into Yii2 core. Just because it is still is (and looks like ever be) experimental framework which does a black magic. It will work for most of cases, but we can't provide a support in cases when it doesn't work, works in improper way, or even worst - affects the application in production.

AspectMock will be developed and supported. It's a really useful tool. But I'm not sure it may fit to everyone,

---

Even though I can recommend specify as it makes tests more descriptive and readable. They are simple and sweet and can bring much better structure into classical unit tests.

[Ragazzo]

Ok, then will make changes and exclude AspectMock from current PR. Will mention it in docs guide for testing.

[Ragazzo]

@qiangxue i think we should raise method visibility LoginForm::getUser to public (for testing purposes too) :)

[qiangxue]

Feel free to do so if needed.

[lisachenko]

I agree with @DavertMik that AspectMock is not very stable yet, because of techniques that are used in Go! AOP framework. However, AspectMock is very promising and interesting project, but it requires more attention and testing to be stable and predictable in all cases. So, it will be better to switch to standard testing framework to be sure that everything will be ok.

BTW, Yii framework can be integrated will go-aop to use an aspect-oriented programming. I have a post about this: http://go.aopphp.com/blog/2013/09/28/aspect-oriented-programming-with-yii/

[Ragazzo]

Reverted aspect-mock changes. Done, ready for review.

[qiangxue]

Cool! Thanks!

[Ragazzo]

Great :) Still need to improve db support)