summaryrefslogtreecommitdiffstats
path: root/Tests/CTestTestCostSerial
diff options
context:
space:
mode:
authorRyan Thornton <ThorntonRyan@JohnDeere.com>2020-03-16 20:16:38 (GMT)
committerRyan Thornton <ThorntonRyan@JohnDeere.com>2020-03-27 14:40:40 (GMT)
commit3b4838b57fc70bd64b29044ccbdf582f14a0574d (patch)
tree906b8b9696ac95ca640044458abeceb358726c70 /Tests/CTestTestCostSerial
parent1ba4cb565eb0bf16a717863ed4945e93468cb146 (diff)
downloadCMake-3b4838b57fc70bd64b29044ccbdf582f14a0574d.zip
CMake-3b4838b57fc70bd64b29044ccbdf582f14a0574d.tar.gz
CMake-3b4838b57fc70bd64b29044ccbdf582f14a0574d.tar.bz2
GoogleTest: Add tests for MultiConfig discovery in PRE_TEST mode
PRE_TEST makes it possible to properly distinguish between test cases that exist only in certain configurations. In the new test scenario, debug tests are disabled in release builds, and release tests are disabled in debug builds when a multi config generator is used. Note, this is a bit of a hack and *only* works for PRE_TEST mode. POST_BUILD makes no attempt to get this right. It preserves the status quo and you obtain the tests that were last discovered. See further discussion in !4078 Ideally, the POST_BUILD behavior could be fixed by using generator expressions in OUTPUT and BYPRODUCT expressions. Then you could do something like: set(ctest_include_file "${ctest_file_base}_include-$<CONFIG>.cmake") set(ctest_tests_file "${ctest_file_base}_tests-$<CONFIG>.cmake") Once #12877 lands, maybe this can be revisited. Co-authored-by: Ryan Thornton <ThorntonRyan@JohnDeere.com> Co-authored-by: Kevin Puetz <PuetzKevinA@JohnDeere.com>
Diffstat (limited to 'Tests/CTestTestCostSerial')
0 files changed, 0 insertions, 0 deletions