PHPUnit tests and output

Hi, The PHPUnit tests for MDB are pretty much finished. Currently the output is not really what Paul Cooper had in mind yet. Here is a little snippet from a mail he send me: > In my mind what I want to get to is > > Page 1: > > List of databases in $dbarray with a check boxes - which database(s) to > test > > List of MDB_*_testcase files with check boxes to choose which test group > to run > > Page 2: > > List of tests in testcases chosen in page 1 with checkboxes to choose > which test(s) should be run > > Page 3: > > Results. Better looking than at the moment. > > Retest button. Choose tests button (i.e. go to Page 2). Choose database > and testcase button (i.e. goto Page 1). > > > However, from what I currently know about PHPUnit, I think it would > require changes in that to achieve these results. Also I won't get this > done by the end of the week ;-) We also intent to make the test runnable from the command line. Also for the output we do have in the test at the moment Paul used HTML_IT. I would want to keep dependencies as small as possible for the tests. And I think that most package developer will be in a similar situation: They want to make the tests easily configurable, make the output nicely structured and don’t want to depend on yet another package. However I don’t know if mixing echo statements with html code is really a good alternative. What are other peoples feelings on this? Should PHPUnit feature some functionality that helps there? Or any other suggestions to best cope with this situation Finally a more general question: How should the dependency on PHPUnit (and any other packages required) for package test suites be handled? It probably doesn't make sense to make them a dependency in the packages package.xml? Or not? Regards, Lukas Smith smith@dybnet.de _______________________________ DybNet Internet Solutions GbR Reuchlinstr. 10-11 Gebäude 4 1.OG Raum 6 (4.1.6) 10553 Berlin Germany Tel. : +49 30 83 22 50 00 Fax : +49 30 83 22 50 07 www.dybnet.de info@dybnet.de