Hi Benjamin,
otherwise, zend_test is doing integration testing and using that soley for
test-driven-development is probably a bad idea, since you test too many
components in conjunction rather than unit-testing a single component in
isolation.
Yep, I came up with that as well. For TDD the
On Mon, Jun 8, 2009 at 8:54 PM, Benjamin Eberlei kont...@beberlei.dewrote:
otherwise, zend_test is doing integration testing and using that soley for
test-driven-development is probably a bad idea, since you test too many
components in conjunction rather than unit-testing a single component in
Hi,
I have a problem that makes TDD with Zend_Test impossible and I don't
know with which release this problem was introduced and how to solve it.
Think of a test case like this:
--
class IndexControllerTest extends
2009/6/8 Ralf Eggert r.egg...@travello.de
[testing non-existent actions]
And now lets presume that the IndexController exists but the
showAction() is not available yet due to the TDD approach. When I run
PHPUnit for this test case I only get this error:
Hi Tim,
I think setting throwExceptions to true on your front controller
in test mode only should fix this, but you won't then be able test
some of the error controller functionality.
That did not help at all. I turned of the ErrorHandler and that worked
partly. Now I don't get any error at
do you use phpunit 3.4? this might be a problem indeed.
otherwise, zend_test is doing integration testing and using that soley for
test-driven-development is probably a bad idea, since you test too many
components in conjunction rather than unit-testing a single component in
isolation.
