itkFEMElement2DC0LinearQuadrilateralStressTestFEMObjectReader
has hard-coded I/O filenames
#4417
Labels
type:Testing
Ensure that the purpose of a class is met/the results on a wide set of test cases are correct
Milestone
Description
The
itkFEMElement2DC0LinearQuadrilateralStressTestFEMObjectReader
test in theFEM
module has hard-coded I/O filenames. Additionally, it is not listed in theFEM
module's test directoryCMakeLists.txt
file, so even if the module and testing are turnedON
when configuring ITK, the build will succeed.Steps to Reproduce
FEM
module and building the tests when configuring.ctest -V -R itkFEMElement2DC0LinearQuadrilateralStressTestFEMObjectReader -C Debug
: no test will be found.Expected behavior
No hard-coded paths should exist: the test should have its I/O arguments specified in the corresponding
CMakeLists.txt
entry.Actual behavior
The
itkFEMElement2DC0LinearQuadrilateralStressTestFEMObjectReader
test in theFEM
module has hard-coded I/O filenames. Additionally, it is not listed in theFEM
module's test directoryCMakeLists.txt
file, so the test is not run even if turningON
theFEM
module and building tests; it will fail if doing so, and adding an entry toCMakeLists.txt
since the I/O filenames are hard-coded.Reproducibility
100%.
Versions
ITK
master
.Environment
Any
Additional Information
Its
Trial.meta
input file is not found on the currentITK
source code tree;SpatialObjects.meta
is found at https://github.com/InsightSoftwareConsortium/ITK/blob/5cf4a7226f1be5133f96fe7fcb49ba1fc367d525/Testing/Data/Input/SpatialObjects.meta.cid.The test (including the hard-coded paths) was added by commit 23f10a9 (Kent Williams authored and @hjmjohnson committed on Jul 15, 2011). It does not look like
Trial.meta
has ever been committed.The text was updated successfully, but these errors were encountered: