O Guia Definitivo do Yii 1.1

Testes
Visão Geral
Note: The testing support described in this chapter requires Yii version 1.1 or higher.
This does not mean, however, that you cannot test applications developed using Yii
1.0.x. There are many great testing frameworks available to help you accomplish this
task, such as PHPUnit, SimpleTest.
Testing is an indispensable process of software development. Whether we are aware of it
or not, we conduct testing all the time when we are developing a Web application. For
example, when we write a class in PHP, we may use some echo or die statement to show
that we implement a method correctly; when we implement a Web page containing a
complex HTML form, we may try entering some test data to ensure the page interacts with
us as expected. More advanced developers would write some code to automate this
testing process so that each time when we need to test something, we just need to call up
the code and let the computer to perform testing for us. This is known as automated
testing, which is the main topic of this chapter.
The testing support provided by Yii includes unit testing and functional testing.
A unit test verifies that a single unit of code is working as expected. In object-oriented
programming, the most basic code unit is a class. A unit test thus mainly needs to verify
that each of the class interface methods works properly. That is, given different input
parameters, the test verifies the method returns expected results. Unit tests are usually
developed by people who write the classes being tested.
A functional test verifies that a feature (e.g. post management in a blog system) is working
as expected. Compared with a unit test, a functional test sits at a higher level because a
feature being tested often involves multiple classes. Functional tests are usually developed
by people who know very well the system requirements (they could be either developers or
quality engineers).
Test-Driven Development
Below we show the development cycles in the so-called test-driven development (TDD):
1. Create a new test that covers a feature to be implemented. The test is expected to
fail at its first execution because the feature has yet to be implemented.
2. Run all tests and make sure the new test fails.
3. Write code to make the new test pass.
4. Run all tests and make sure they all pass.
5. Refactor the code that is newly written and make sure the tests still pass.
Repeat step 1 to 5 to push forward the functionality implementation.
Test Environment Setup