Fix tests

[schuhschuh]

The following tests require input data that is currently not set up:

• [ ] Modules/Image/test/testConvolutionFunction.cc
• [ ] Modules/Image/test/testDownsampling.cc
• [ ] Modules/PointSet/test/testEdgeTable.cc

Consider use of Git LFS for storage of test data files

The following tests have to be rewritten to use gtest:

• [ ] Modules/Image/test/testInterpolateExtrapolateImageFunction.cc

The following tests fail:

• [ ] Modules/Numerics/test/testPolynomial.cc

[ghisvail]

How big are the test data?

[schuhschuh]

How big are the test data?

Currently there isn't too much, however, some reasonably sized images for system tests may be useful. In any case, it's good to have a means of dealing with large data files. May these be test input/baseline data or auxiliary data files such as a brain atlas required by an application such as Draw-EM.

We can either follow the path of ITK/VTK and use the ExternalData CMake module which allows storage of data anywhere (but we'd have to think about where) or use GitHub's Git LFS (fine with me considering that the repo lives on GitHub and all data files need to be public anyway).

[ghisvail]

My personal take on this is that big sized data should not be required for running unit tests. The main goal of the project repository should be to host code, which can be quickly checked out and potentially [unit]tested.

So perhaps the issue of setting up these integration / system tests you mentioned and hosting the required static data should be considered a different issue?