Hi, I know this could be the dummiest question ever, but i will ask same way.
I'm currently using a bootstrao for my PHPUnit tests similar to the one here: http://framework.zend.com/manual/2.2/en/tutorials/unittesting.html But i was taking a look at Zend\Test\PHPUnit\Controller\AbstractControllerTestCase and i notice that except the part that init the autoloader everything else did at bootstrap is also did at AbstractControllerTestCase (just with a feel diferences on naming conventions) you just need to call setApplicationConfig on a test that extends AbstractControllerTestCase to load your config file. So my point is, whats the real reason to include all this code on bootstrap if we cab just extend all tests from AbstractHttpControllerTestCase or AbstractConsoleControllerTestCase? There is a reason to not do that? I mean... there is a reason to just use AbstractHttpControllerTestCase to test controllers and not models or any other class? Since AbstractControllerTestCase extends PHPUnit_Framework_TestCase we won't have all the funcionality present in PHPUnit_Framework_TestCase plus access to serviceManager and everything else? Won't be easy too bootstrap the PHPUnit with just the autoloader? Or i'm just making a really big mess? -- View this message in context: http://zend-framework-community.634137.n4.nabble.com/Dummie-Question-About-Unit-Test-Bootstrap-tp4660794.html Sent from the Zend Framework mailing list archive at Nabble.com. -- List: [email protected] Info: http://framework.zend.com/archives Unsubscribe: [email protected]
