 |
 |
Hi Edo Yes, we should have tests that return bools etc. CTest actually needs executables that return success or failure. This is how the test scripts that Evgueni mentioned behave. Have a look at the .travis.yml. Obviously, there’s only very few right now but it should be easy to add these to CMakeLists.txt (using the relevant PYTHON_EXECUTABLE variable set). That would be a first step. I think we should then use something like nosetest for Python. This can again easily be called by CTest. Kris From: CCP-PETMR Developers list [mailto:[log in to unmask]] On Behalf Of Evgueni Ovtchinnikov Sent: 09 August 2017 15:44 To: [log in to unmask] Subject: Re: Test after build Actually not. Our demo scripts indeed require visual inspection, but we also have test scripts in src/x*/p*/tests that do not. From: CCP-PETMR Developers list [mailto:[log in to unmask]] On Behalf Of Edoardo Pasca Sent: 09 August 2017 14:40 To: [log in to unmask]<mailto:[log in to unmask]> Subject: Test after build Hallo I’m starting to think how to do the tests with Ctest. Now, most if not all of our tests require visual inspection! I believe we should make tests that return a Boolean: passed or not, which can’t be achieved with a visual inspection. Maybe we could modify them to output a sort of pass/no-pass? Ideas? Edo -- Edoardo Pasca, PhD Visual Analytics and Imaging Systems Group Scientific Computing Department, STFC Rutherford Appleton Laboratoty 0044 (0)1235 44 5660 :wq