Jody Garnett ha scritto:
The code coverage is non existent actually, it's just 4%.
There are ways to test a GUI for its basic, like
http://www.uispec4j.org/, thought this site contains a wider list:
http://java-source.net/open-source/testing-toolsI absolutely agree that unit testing a GUI cannot be as deep as
unit testing a library class, it ends up being more "smoke testing"
to prevent major issues in the UI.
The ogc EMF models are another example of untested module, thought
in that case there is very little to test since the code is fully
machine generated and has no logic whatsoever.
We can discuss this and come up with different rules for different
modules, but I have to say no testing at all makes me quite worried.
Cheers
Andrea
PS: btw, a minor point: this discussion should take place on the devel list
--
Andrea Aime
OpenGeo -
http://opengeo.orgExpert service straight from the developers.
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf_______________________________________________
Geotools-gt2-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users