Doctrine_manual-1-2-en

Chapter 27: Unit Testing 358
}
}
// This produces a failing test
public function testTest()
{
$this->assertTrue($this->myModel->exists());
$this->assertEqual(0, 1);
$this->assertIdentical(0, '0');
$this->assertNotEqual(1, 2);
$this->assertTrue((5 < 1));
$this->assertFalse((1 > 2));
}
class Model1 extends Doctrine_Record
{
}
class Model2 extends Doctrine_Record
{
}
The model definitions can be included directly in the test case file or they can be put in
/path/to/co/doctrine/tests/models and they will be autoloaded for you.
Once you are finished writing your test be sure to add it to run.php like the following.
Listing
27-8
$test->addTestCase(new Doctrine_Sample_TestCase());
Now when you execute run.php you will see the new failure reported to you.
Ticket Tests
In Doctrine it is common practice to commit a failing test case for each individual ticket that
is reported in trac. These test cases are automatically added to run.php by reading all test
case files found in the /path/to/co/doctrine/tests/Ticket/ folder.
You can create a new ticket test case easily from the CLI:
Listing
27-9
$ php run.php --ticket 9999
Listing
27-10
If the ticket number 9999 doesn't already exist then the blank test case class will be
generated for you at /path/to/co/doctrine/tests/Ticket/9999TestCase.php.
class Doctrine_Ticket_9999_TestCase extends Doctrine_UnitTestCase
{
}
Methods for testing
Assert Equal
Listing
27-11
// ...
public function test1Equals1()
{
----------------- Brought to you by