Comments on: Accessing Database in Unit Test with sfDoctrine http://wp.omeeza.com/sunhwan/2007/07/30/accessing-database-in-unit-test-with-sfdoctrine/ Just another wp.omeeza.com weblog Fri, 30 Jul 2010 00:53:32 +0000 http://wordpress.org/?v=wordpress-mu-1.2.5 By: Kaizenlog » Database 30/07/2007 http://wp.omeeza.com/sunhwan/2007/07/30/accessing-database-in-unit-test-with-sfdoctrine/#comment-31 Kaizenlog » Database 30/07/2007 Fri, 28 Sep 2007 03:15:20 +0000 http://wp.omeeza.com/sunhwan/2007/07/30/accessing-database-in-unit-test-with-sfdoctrine/#comment-31 <p>[...] Accessing Database in Unit Test with sfDoctrine By sunhwan After made autoloading sfDoctrine available last week, I was thinking accessing database or pretending it (for test purpose) is surely easy. However, it wasn’t easy at all. So, here is the record of my struggle and, hopefully, … sunhwan - http://wp.omeeza.com/sunhwan [...]</p> […] Accessing Database in Unit Test with sfDoctrine By sunhwan After made autoloading sfDoctrine available last week, I was thinking accessing database or pretending it (for test purpose) is surely easy. However, it wasn’t easy at all. So, here is the record of my struggle and, hopefully, … sunhwan - http://wp.omeeza.com/sunhwan […]

]]> By: Jonathan Ding http://wp.omeeza.com/sunhwan/2007/07/30/accessing-database-in-unit-test-with-sfdoctrine/#comment-29 Jonathan Ding Thu, 27 Sep 2007 05:57:17 +0000 http://wp.omeeza.com/sunhwan/2007/07/30/accessing-database-in-unit-test-with-sfdoctrine/#comment-29 <p>Your article looks good. And I find the solution you want, as below. The major idea is that you should initialize the sfContext to get all dynamic stuff get created, while simple include the config.php to get all static settings correct.</p> <p>== the code == require_once(dirname(<strong>FILE</strong>).'/../bootstrap/unit.php');</p> <p>define('SF_ROOT_DIR', realpath(dirname(<strong>FILE</strong>).'/..')); define('SF_APP', 'frontend');</p> <p>// load the compiled Doctrine library require_once(SF_ROOT_DIR.DIRECTORY_SEPARATOR.'lib'.DIRECTORY_SEPARATOR.'Doctrine.compiled.php');</p> <p>// it will configure the system, including autoload require_once(SF_ROOT_DIR.DIRECTORY_SEPARATOR.'apps'.DIRECTORY_SEPARATOR.SF_APP.DIRECTORY_SEPARATOR.'config'.DIRECTORY_SEPARATOR.'config.php');</p> <p>// This initializes the context, it will initialize the database for you sfContext::getInstance();</p> <p>$t = new lime_test(1, new lime_output_color()) // your tests ...</p> Your article looks good. And I find the solution you want, as below. The major idea is that you should initialize the sfContext to get all dynamic stuff get created, while simple include the config.php to get all static settings correct.

== the code == require_once(dirname(FILE).’/../bootstrap/unit.php’);

define(’SF_ROOT_DIR’, realpath(dirname(FILE).’/..’)); define(’SF_APP’, ‘frontend’);

// load the compiled Doctrine library require_once(SF_ROOT_DIR.DIRECTORY_SEPARATOR.’lib’.DIRECTORY_SEPARATOR.’Doctrine.compiled.php’);

// it will configure the system, including autoload require_once(SF_ROOT_DIR.DIRECTORY_SEPARATOR.’apps’.DIRECTORY_SEPARATOR.SF_APP.DIRECTORY_SEPARATOR.’config’.DIRECTORY_SEPARATOR.’config.php’);

// This initializes the context, it will initialize the database for you sfContext::getInstance();

$t = new lime_test(1, new lime_output_color()) // your tests …

]]> By: Jonathan Ding http://wp.omeeza.com/sunhwan/2007/07/30/accessing-database-in-unit-test-with-sfdoctrine/#comment-28 Jonathan Ding Thu, 27 Sep 2007 05:56:12 +0000 http://wp.omeeza.com/sunhwan/2007/07/30/accessing-database-in-unit-test-with-sfdoctrine/#comment-28 <p>Your article looks good. And I find the solution you want, as below. The major idea is that you should initialize the sfContext to get all dynamic stuff get created, while simple include the config.php to get all static settings correct.</p> Your article looks good. And I find the solution you want, as below. The major idea is that you should initialize the sfContext to get all dynamic stuff get created, while simple include the config.php to get all static settings correct.

]]>