I bounced your email back to the list. I hope this is ok....
> I understand you are also working on improvising the test suite. i would be happy to work with if you are interested in collaborating any portion of the work.
I have refactored the authentication part and add some new authentication methods like shib. I use test driven development for the programming. I choose phpunit because it is already integrated in NetBeans.
> i have been in this project for couple of weeks now and i have made an attempt to somewhat understand the vufind application. i am also trying to learn how phpunit works and is integrated with vufind for the existing test suites.
> let me know how you would like to co-ordinate and also if i need to learn anything else before starting work on this.. any advice on how to approach this will be great...
I think the best way, is simply to write tests for classes that don't have any. In that way you will get familiar with phpunit. You can also use the existing tests and add tests or change it. Just do it :-)! I am the author of the tests and it is not a problem for me if you change it and commit it back to trunk.
After you get some experiences with phpunit, we should have some plan, how to group the different parts of vufind. For example it would be great to group all tests for the authentication to one test suite. We should also have some automatism to start the test suites (separate and all at once). I think ant could be a nice choose or if you prefer good old bash or php itself.
After that it we need to convince other developers to add tests, since when they write new classes. This is the hardest part :-).
Some things would not be testable with phpunit, like logout, ajax stuff, searches. There exists automated test clients like HtmlUnit, but I am not sure if it is necessary to add such top level tests...
Have a nice day!