2007/02/05
There were many interesting things for me: http://www.todoorelse.com/gtd/index.html
Enjoy 
Input related to Unit Testing on different projects/experiences you have worked on is needed. I talked with some people here in the office and a pattern/common points of how usually our approach is done couldn't be found. Reasons for that are many:
- it depends very much on type of code (core code, business logic code, JDBC code..)
- requirements concerning to test are different on each project.
- make effective unit test on legacy code is very difficult.
- other complicated situation is when you don't have clear separation between code you have been developing and legacy code (as an definition of an interface between them or a even a module, for instance).
All of these reasons make your approach be different for each situation.
But still some patterns could be found, like on AMS Development, it is required to code coverage of new code should be at least 80% and it is not required to cover some kind of code, like getters and setters.
On other projects (specially external ones), a pattern/common points on Unit Testing that AQRIS developers always take care of, no matter if it is a client requirement, is not yet defined/mapped.
Please, share experience you have on different projects you have been working on in order to find some common tasks we usually do concerning unit testing.