+1 to Thomas and Graham: on one hand "big picture javadocs" should be present (I'm thinking of package-level javadoc, that can be done, but it seems most people don't know that), as an introduction to a new programmer to quickly understand the API, and on the other hand test cases are a better way to document details of behaviour. I'm still waiting for a tool that understands mockito assertions and generates some kind of documentation (including sequence diagrams).

--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
[email protected]
http://tidalwave.it - http://fabriziogiudici.it

--
You received this message because you are subscribed to the Google Groups "Java 
Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/javaposse?hl=en.

Reply via email to