Feature #1290: === Core: framework ===
core functional test machinery: simplify, or at least explain
|Status:||Resolved||Start date:||27 Apr 2016|
|Category:||-||Estimated time:||17.00 hours|
I find it hard if not impossible to understand the functional test machinery.
It's already somewhat tricky at CMake level, and then there come several layers of C++.
We have core_functional_tests, CoreFunctionalTest, and CORE_FUNCTIONAL_TEST: how do they relate to each other?
At the very least, we need more explanations in the code.
Also, reconsider renaming some files/classes/functions.
UPPERCASE_NAMES are conventionally reserved for preprocessor macros - why use them for an ordinary function?
#4 Updated by wuttke almost 4 years ago
- Status changed from Sprint to Backlog
Explain commands 'ctest -R', 'bin/CoreSuite <test>, ...[done in http://bornagainproject.org/documentation/troubleshooting]
- When comparison with reference data fails, print a hint where the images are located and how to visualize them