Martin Desruisseaux wrote:
Bryce L Nordgren a écrit :
There's significant opportunity to create resuable unit tests for the
GeoAPI geometry interfaces to determine implementation compliance and
correctness. This potential presumably exists for other GeoAPI
modules as
well. For now, let's keep it simple: should the geometry tests live
in the
GeoTools project, the GeoAPI project, or in a third project?
I would like a test suite in the GeoAPI project, if we can write it
abstract enough so that it doesn't contains any explicit reference to
any implementation.
If we can find volunter time, we may try to move some Geotools tests
from the referencing module (at least the parts that do not involve
any geotools-specific API) as a proof of concept.
That sounds great, for the GeoAPI project - in that test cases are a
great way to specify things in a manner stronger then just reading
javadocs :-)
Problem is this will make geotools much harder to maintain for anyone
who is not a member of both GeoTools and GeoAPI. Already on the FM
branch this kind of things is proving annoying, if you move test cases
over it will be much worse.
-1 (Be nice to your developers)
Jody
-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid7521&bid$8729&dat1642
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
