Well I fooled with Unit Testing in Sakai for a few hours and kind of came to a dead end. It was pretty fun and the basic stuff worked. My problem is that I just don’t know where to stop when creating mock versions of stuff. I looked at unit tests in the gradebook and common and there is not much interaction witht he rest of Sakai – I want to create unit tests that can interact with the rest of Sakai. But that means firing up components somehow (or mocking that up), firing up component manager (or mocking that up) etc etc. The problem is that with the structure of unit tests it seems that everyone who writes a unit test is responsible for mocking up the entire rest of the system. This is icky when dealing with a system as large as Sakai with a goal of a rich framework that *everything* depends on. So we will need to develop a way to make unit testing easier. Someone other than me will need to figure this out.
But here are my notes. Thanks to Josh and Lance for their examples.