Thanks, Marcos. I think separating tests into self-contained tests and
tests requiring external resources would be quite useful and make it
easier to developers outside Unidata to contribute to Thredds. This is a
pattern I have seen in other open-source projects. Crafting
self-contained test fixtures requires care and effort, but they will be
run more often and more widely.
Thanks for confirming that my test problems are not just mine!
Kind regards,
Ben.
On 20/08/12 22:43, Marcos Hermida wrote:
Hi Ben,
unfortunately and besides the compiling errors the Thredds units test
rely heavily in our local environment and they would be really hard to
run out of it.
Actually, you would also need to be able to create the same environment
with the same data files we have here as we use catalogs, paths and urls
containing environment dependent locations and test against specific
expected content in those data files.
Something we have in mind is create two sets of tests: one would be a
set of tests that everybody could easily run and the other set would be
our local tests created to reproduce particular issues users have
reported. So, in a default maven build all tests in the first set
should run in any environment and we could run the second set in our
internal continuous integration environment. However, as the test data
files should be part of the source code download as resources for the
tests is hard to choose a set of files and datasets to keep that
download in a reasonable size and provide a comprehensive code coverage.
Cheers!
On 08/20/2012 03:09 AM, Ben Caradoc-Davies wrote:
Is there a procedure for running the Thredds 4.2 unit tests? Many do
not compile. I think I might be missing some modules. Do I need
opendap and ui?
I am looking at the 4.2 branch. I can build and run Thredds. I would
like to be able to run the unit tests, but they do not compile, even
if I add all the lib jars such as spring-test-2.5 that are not bundled
in the Thredds war. I am using Eclipse not NetBeans but I do not think
this is the problem.
There are other failures. For example, lib contains netcdf-4.2, but
some unit tests use CompareNetcdf which is only in netcdf-4.1.
Kind regards,
_______________________________________________
thredds mailing list
thredds@xxxxxxxxxxxxxxxx
For list information or to unsubscribe, visit:
http://www.unidata.ucar.edu/mailing_lists/
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@xxxxxxxx>
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
