- Last edited January 9, 2003 |
Currently in fantastic project DoingIt. Not currently available for consulting.
Using TurbineTorque?, and TurbineMaven? (very cool.. thanks to JoeW)
Recently been seen playing with Tibco, OpenSymphony WebWork?, SiteMesh, DbUnit.
[email protected] www.lizardsoftware.com/
Embarrasing photo "all I want for xmas is XP": xpday.xpdeveloper.com/photos/103-0342_IMG.JPG
Random thoughts on Test Overspecification:
I've noticed that if a testMethod covers many implementation methods then when you refactor the implementation you dont have to change the testClass as often. Is this bad practice? Can fewer 'larger' tests help make refactoring easier? This is counter to the patern of have many testMethods for every implementation method.
Perhaps I should not test all these implementation methods? Should I make them private and not test them individually but rather let the larger test cover them? (more like black box testing?)
"Ben - since your server hosts xpday, please can you make it available, or arrange for the transfer to Oli's host? Sadly, we can't email you as this is also hosted on your server - thanks, PaulS."
Server back up. the data center had a power failure. Typical.. go on holidays to the whitsundays and all goes to pot while you are sitting on the beach.
- Last edited January 9, 2003 |