  | Mailing List | | Home | | Forum Home | | JBoss - Java Application Server | | Tomcat - JSP/Servlet container | | Struts - A MVC web framework | | iText - An open source PDF Java Library | | JDOM - JDOM XML Parser | | JSP - A mailing list about Java Server Pages specification and reference | | J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition | | J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog | | Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology | |
Struts & Hibernate
|
|
|
  | | | Unit Testing BOs, TOs (Getters & Setters) | Unit Testing BOs, TOs (Getters & Setters) 2005-05-21 - By Marvin Toll
Back I'm interested in best practices around automated unit testing of getters and setters for organizations that strive for near 100% code coverage, and are using core patterns including BOs and TOs.
Organizations that *do* attempt to fire getters/setters: What is the strategy? Are these all hand-coded?
Organizations that do *not* attempt testing these methods: How do they report their code coverage? For instance, do they "back-out" the amount of code represented by getters/setters and then report the percentage of remaining code covered? Or - do they lower the goal to something considerably less than 100%?
Is anyone actually striving for near 100% code coverage?
_Marvin
==================================================================== Companion Site: http://www.corej2eepatterns.com J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
|
|
 |