Hi Benjamin, I just saw how you organized the test framework, and I have several questions before I start using it (I'd like to optimize DeleteDuplicateGeometriesPlugIn before 1.5.1 release, which is an excellent opportunity to test your Framework) :
- did you see there is already a package named jumptest in src ? I did not pay attention before, but I think we have to care if we want to keep the whole src hierarchy consistent. - Do you think existing tests (src/jumptest) could easily be merged (or simply gathered) in the same package as yours ? - What is the best place for the test framework. I think I would have created the package at a higher level (maybe src/test or src/jumptest as the existing one). But if there are argument for org.openjump.test, it is also ok. - What is more important is to be able to separate test classes from core classes at release time. If we put test classes beside plugins as you did for UnionByAttributePlugIn, it will be difficult to separate them isn't it ? Would it make sens to just prefix tested class names like test/com/(vividsolutions?)/jump/workbench/ui/plugin/ExistingPlugInTest test/org/openjump/core/ui/plugin/NewPlugInTest Any opinion ? Michaël ------------------------------------------------------------------------------ RSA(R) Conference 2012 Mar 27 - Feb 2 Save $400 by Jan. 27 Register now! http://p.sf.net/sfu/rsa-sfdev2dev2 _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
