$loader = new Loader();
        $this->application = $loader->loadApplication();
        $this->bootstrap = $loader->getBootstrap();

Best regards
Christian

Actually there's a solution shown in the last of Zend Casts (which deals with creating two instances of Zend_Application). Gotta stick to that until there is a better way doing it.

This source code doesn't work.

When I set up a new Zend Framework project from these sources and run PHPUnit test with Zend Studio, I get several errors :

First, the Zend_Test_PHPUnit_ControllerTestCase class is not known : “Fatal error: Class ‘Zend_Test_PHPUnit_ControllerTestCase’ not found in D:\…\tests\application\models\UserTest.php”.
Ok, I add a require_once ‘Zend/Test/PHPUnit/ControllerTestCase.php’; in my UserTest.php file.

So, I no longer have this error, but a new error for the model on $u = new User(); : “Class ‘User’ not found in D:\…\tests\application\models\UserTest.php”.

I can still not add a require_once for each class of my project.
The bootstrap does not even use.

Do you have any idea of the origin of this problem ?
Is this related to the use of Zend Studio ?
Is there anything else to add or modify to run this project ?

Thank you in advance for your help.

Best regards.

Stéphan.

I'm trying to integrate ZF and Doctrine in a testable way, and I have some trouble which comes back to what Sebastian Montero wrote. What I fail to see is a way of bootstrapping my test suite so it could be used for testing both controllers and models.

In this screencast Zend_Application is instantiated in /tests/application/bootstrap.php so the CLI code runs only once. Yet in ZC-25 which covers controller testing it's instantiated in setUp method of a ControllerTestCase class.

The problem is that if you create an instance of Zend_Application in bootstrap.php and then you try to test your controllers it's all messed up. Though everything works fine in browser, running $this->dispatch('/uri') ends up with "No default module" error, and when you fix that it cannot find your controller plugins and then it has trouble finding layout resource and so on and so forth. So you basically have to bootstrap your application twice which is no good.

On the other hand, you can move everything into your setUp method. But then you'll have 'build-all-reload' CLI command running for every single test method which also is a bad thing.

What I do is I actually run 'build-all-reload' before instantiating the application:

<?php

define('APPLICATION_PATH', realpath(dirname(__FILE__) . '/../../application'));

define('APPLICATION_ENV', 'testing');

set_include_path(implode(PATH_SEPARATOR, array(
    realpath(APPLICATION_PATH . '/../library'),
    realpath(APPLICATION_PATH . '/models'),
    get_include_path(),
)));


require_once 'Zend/Application.php';
require_once 'Zend/Config/Ini.php';
require_once 'Doctrine.php';
require_once 'ControllerTestCase.php';


$config = new Zend_Config_Ini(APPLICATION_PATH.'/configs/application.ini', APPLICATION_ENV);
$dbConfig       = $config->db->toArray();
$doctrineConfig = $config->doctrine->toArray();

spl_autoload_register(array('Doctrine', 'autoload'));

$manager = Doctrine_Manager::getInstance();
$manager->setAttribute(Doctrine::ATTR_MODEL_LOADING, Doctrine::MODEL_LOADING_AGGRESSIVE);
$manager->setAttribute(Doctrine::ATTR_VALIDATE, Doctrine::VALIDATE_ALL);
$manager->setAttribute(Doctrine::ATTR_EXPORT, Doctrine::EXPORT_ALL);
$manager->setAttribute(Doctrine::ATTR_QUOTE_IDENTIFIER, true);

$dsn = sprintf("mysql://%s:%s@%s/%s",
    $dbConfig['username'],
    $dbConfig['password'],
    $dbConfig['host'],
    $dbConfig['dbname']
);

$connection = $manager->connection($dsn);
$connection->setAttribute(Doctrine::ATTR_USE_NATIVE_ENUM, true);

$cli = new Doctrine_Cli($doctrineConfig);
@$cli->run(array('Doctrine', 'build-all-reload', 'force'));

And then I create an instance of Zend_Application normally:

<?php

require_once 'Zend/Test/PHPUnit/ControllerTestCase.php';

abstract class ControllerTestCase extends Zend_Test_PHPUnit_ControllerTestCase
{
    protected $application = NULL;

    public function setUp()
    {
        $this->bootstrap = array($this, 'appBootstrap');
        parent::setUp();
    }

    public function appBootstrap()
    {
        $this->application = new Zend_Application(
            APPLICATION_ENV,
            APPLICATION_PATH . '/configs/application.ini'
        );
        $this->application->bootstrap();
    }
}

I wonder what you guys think about it and if there's a better way doing this.

It seems like this is the issue, I've created another table, generated the model for it and tested it successfully.
by the way, the new class name is: 'Project'

I've read several reports a silly bug where models that start with letters before "D" aren't loaded... I'm not sure if that's your issue though...

in the application.ini you defined some settings:

doctrine.generate_models_options.pearStyle = true
doctrine.generate_models_options.generateTableClasses = false
doctrine.generate_models_options.generateBaseClasses = true
doctrine.generate_models_options.baseClassPrefix = "Base_"
doctrine.generate_models_options.baseClassesDirectory =
doctrine.generate_models_options.classPrefixFiles = false
doctrine.generate_models_options.classPrefix = "Model_"

If I try to integrate phpunit testing with the setup explained in previous tutorials and the one you provide in this video
example:

class ArticleTest extends Zend_Test_PHPUnit_ControllerTestCase {
.
.
.
public function testFindAll() {
        $article = new Model_Article();
        $obj = $article->findAll($this->lang);
        $this->assertTrue( count($obj) > 0);
    }

I get this error:

PHPUnit 3.4.9 by Sebastian Bergmann.

PHP Fatal error:  Class 'Model_Article' not found in C:\server\www\zend_site\t
ests\application\models\ArticleTest.php on line 23

What am I doing wrong?

PHPUnit 3.4.8 by Sebastian Bergmann.

.

Time: 46 seconds, Memory: 32.00Mb

OK (1 test, 6 assertions)

Generating code coverage report, this may take a moment.
Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 35 bytes) in /usr/share/php/PHPUnit/Util/Report/Node/File.php on line 644

Call Stack:
    0.0006      62840   1. {main}() /usr/bin/phpunit:0
    0.1008    4498284   2. PHPUnit_TextUI_Command::main() /usr/bin/phpunit:54
    0.1008    4499016   3. PHPUnit_TextUI_Command->run() /usr/share/php/PHPUnit/TextUI/Command.php:146
   42.4558   21921616   4. PHPUnit_TextUI_TestRunner->doRun() /usr/share/php/PHPUnit/TextUI/Command.php:213
   46.2234   30628640   5. PHPUnit_Util_Report::render() /usr/share/php/PHPUnit/TextUI/TestRunner.php:478
   46.2948   31323220   6. PHPUnit_Util_Report::addItems() /usr/share/php/PHPUnit/Util/Report.php:118
   46.2986   31358240   7. PHPUnit_Util_Report::addItems() /usr/share/php/PHPUnit/Util/Report.php:154
   46.3014   31385764   8. PHPUnit_Util_Report::addItems() /usr/share/php/PHPUnit/Util/Report.php:154
   46.5328   33319972   9. PHPUnit_Util_Report_Node_Directory->addFile() /usr/share/php/PHPUnit/Util/Report.php:146
   46.5328   33321944  10. PHPUnit_Util_Report_Node_File->__construct() /usr/share/php/PHPUnit/Util/Report/Node/Directory.php:147
   46.5329   33322732  11. PHPUnit_Util_Report_Node_File->loadFile() /usr/share/php/PHPUnit/Util/Report/Node/File.php:168
   46.5332   33365436  12. token_get_all() /usr/share/php/PHPUnit/Util/Report/Node/File.php:644

Any idea??

And how about using doctrine mock drivers or sqlite memory database? to solve that problem.

Thanks!

you can certainly do it in that manner, however as you start writing hundreds of tests,  you might find nuking your db every time to slow you down. To do it though, you could just modify your startUp and tearDown methods for the model tests.

thanks