WIP: Refactor test/CMakeLists.txt to adhere to ITK module convention

[axel-grc]

• Changed the main function in various test files to specific test function names .
• Updated the CMakeLists of tests to follow itk convention with createtestdriver

Close #896

[axel-grc]

There is a problem with the example tests: with the ITK convention, tests are dispatched by the test driver and must provide an entrypoint like int (int,char**). The examples are standalone programs with a main(), and I don’t think it’s a good idea to rewrite their main just to fit the test driver pattern.

For now, I kept the previous approach only for examples: build each example as its own executable and register it with CTest via itkTestDriver.

Do you have any insight on this, @SimonRit

[SimonRit]

There is a problem with the example tests: with the ITK convention, tests are dispatched by the test driver and must provide an entrypoint like int (int,char**). The examples are standalone programs with a main(), and I don’t think it’s a good idea to rewrite their main just to fit the test driver pattern.

For now, I kept the previous approach only for examples: build each example as its own executable and register it with CTest via itkTestDriver.

Do you have any insight on this, @SimonRit

I'm not following. This seems to be the convention of a main function in C which is ok to adopt for all examples as is done in FirstReconstruction:
https://github.com/RTKConsortium/RTK/blob/main/examples/FirstReconstruction/FirstCudaReconstruction.cxx#L12