Fooling with uPortal Notes
This is just raw notes from working with Adrian at Lancaster. Ultimately this was me getting up2.4 to work – Adrian did this with up2.5 and after a while I switched and helped him.
Archive for October 2005
UNIT Testing In Sakai
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.
Sakai Developer QuickStart
The big picture/outline:
http://cvs.sakaiproject.org/release/2.0.1/SourceInstallGuide.html
The attached script is the “magic developer bootstrap thing” – when it runs – you are in great shape.
Pre-requisites
SVN for Mac:
http://metissian.com/projects/macosx/subversion/
Maven
http://maven.apache.org/start/install.html
Add this to your .bashrc_login (or equivalent)
JAVA_OPTS='-server -Xms512m -Xmx512m -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCTimeStamps'; export JAVA_OPTS;
