I'm want to get in the habbit of writing unit test for [1] the new classes I
create for OpenJUMP, and [2] the existing JUMP/OpenJUMP classes that I work
with. I am not an expert with JUnit, so I was hoping to get some help from
other OpenJUMP Developers. (If there are some of the GeoTools developers
listening and they would be willing to tell me how JUnit tests are used and
organized on the GeoTools project, that would be appreciated also.)
My main question deals with how to organize the unit tests. One of my books
on JUnit suggests putting the tests in a separate, but identical package
structure. As an example, a JUnit test for the
com.vividsolutions.feature.Feature interface would be found in
tests.com.vivdsolutions.feature.Feature package, and would be named
com.vividsolutions.feature.FeatureTest.
Does this sound like a good plan for organizing units tests for OpenJUMP? If
we get the different development teams to agree on some type of standard we
could even share our unit tests.
Thanks for the help.
The Sunburned Surveyor
P.S. - I'm in the process of writing unit tests for the RenderingManager and
LayerRenderer classes. I'll make these available when they are complete.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
