Gian -
Does this mean the database issue is not covered
in the Unit Testing chapter?
If this is the case what is in your opinion the
strategy to adopt for Unit Testing with database
driven web apps. Or do you have any favourite
litterature on this issue?
It does
NOT mean that database issues are skipped, including in the
JUnit chapter. I cover testing both entity and boundary classes (which includes data access classes) and how to establish a
JDBC fixture.
Persistence appears in the "What's Not in this Book" chapter because I don't go into great detail on persistence frameworks, like JDO, Hibernate, and others. I do cover migrating to
EJB's, but only in 1 chapter.
Neal Ford<br />Author, <i>Art of Java Web Development: Struts, Tapestry, Commons, Velocity, JUnit, Axis, Cocoon, InternetBeans, WebWork</i><br /><a href="http://www.nealford.com" target="_blank" rel="nofollow">www.nealford.com</a>