I think this is part of a bigger problem in general actually.
As noted here: http://framework.zend.com/issues/browse/ZF-417
I really think the framework could benefit from a component driven test
manager. PHPUnit3 is pretty great, but its overall goodness is to test
code and suites.. and I think our benefit here would be to create a
testrunner that is 'component driven'. This would allow for newbies to
get up to speed quicker and also create a framework for new tests to be
written. Something like 'exclude slow tests' could be a feature of such
test runner.
I personally like my spaghetti in an Italian restaurant, no so much in
the mess of unit tests we have ;) But in general, thats what I feel
like I am looking at everytime I sit to write unit tests.
After this next round of component development that I am currently
working on, I would definitely like to put some cycles into
ZFTestManager again (as well as code cleanup as per the coding
standards). But alas, that prob wont be till December.
-ralph
Andries Seutens wrote:
Hi,
I would like to bring this to your attention:
The current tests folder in the incubator seems to be really messy. When
running AllTests.php, it seems like the configuration file from the core
tests is included as well, causing constants to already be defined, and
producing tons of error messages. I have attached report.txt, which
shows the current errors.
There also seem to be some missing Zend_Db skiptests.
Anyone cares to fix these issues?
Best,
------------------------------------------------------------------------
Gecontroleerd op virussen door de JOJO Secure Gateway.
