In my latest checkin I merged PHPUnit for unit testing Fez. So far there
are tests for the DuplicatesReport stuff that I'm developing. You can run
them like this:
$ cd trunk/test
$ php DuplicatesReportTests.php
This runs a bunch of tests and is pretty quiet if all goes well. You can
also run phpunit and pass it a classname of one of the individual test
files. I hope to tidy up the sturcture of it all and organise into
test-suites as time goes on.
You can read all about PHPUnit here:
The ultimate goal is to set up an automated test application so that we can
take a lot of the work out of Fez release testing by at least satisfying
that all the primary assumtpions and functions are running ok. However, it
will be a lot of work to fill in tests for all of Fez retrospectively. For
now, when writing code, try to write a test-suite to look after all the bits
and pieces in your code.
For stuff that relies on objects in fedora and the Fez database, I would
like to come up with a standard way to do this e.g. a standard test
community and collection setup solely for ingesting special test objects and
things. Suggestions and stories of relevent experiences are welcome.
Get latest updates about Open Source Projects, Conferences and News.