--- On Tue, 8/11/09, Alexandre Emsenhuber <alex.emsenhuber(a)bluewin.ch> wrote:
+1, we could maybe write our own test system that can
be
based on the
new Maintenance class, since we already some test scripts
in /
maintenance/ (cdb-test.php, fuzz-tester.php,
parserTests.php,
preprocessorFuzzTest.php and syntaxChecker.php). Porting
tests such as
parser to PHPUnit is a pain, since it has no native way to
write a
test suite that has a "unknow" number of tests to run.
Rewriting parserTests as php unit tests would be a horrible waste of time. parserTests
works and it provides a reasonable service. One problem, however, is how do we fix the
parser? It seems it is a pretty complex code system (when I ran a MacGyver test on
parserTests, 141 files were accessed, most of which are associated with the parser). I
have been thinking about this, but those thoughts are not yet sufficiently clear to make
public yet.
On the other hand, taking the parserTests route and doing all of our own test
infrastructure would also be a good deal of work. There are tools out there (phpuint and
prove) that are useful. In my view creating a test infrastructure from scratch would
unnecessarily waste time and resources.
Dan