Joe Kaplan

I've created a new package and I'm examining the HelloWorld object in that package. Particular looking at how Unit tests work.

By default all the tests pass. If I build RUN_TESTS everything looks good and the output shows the tests pass. If I add

"REQUIRE(1 == 0);" and then build RUN_TESTS

It shows the tests failed but then posts a bunch of CTEST errors. The error list also shows an MSB3073 from Micorosft.Cppcommon.targets.

See Screenshots attached. I'm wondering if this is unusual, or if this is normal and to be expected. If took some fussing, but this is now the only unusual behavior in my Dev Environment. Want to check it out before I start coding in earnest. If anyone has any thoughts, please let me know. Thanks!

Test Fail - Causes Errors.JPG

Test Fail - Causes Error.JPG

Test Pass - All Good.JPG

I've created a new package and I'm examining the HelloWorld object in that package.  Particular looking at how Unit tests work.

By default all the tests pass.  If I build RUN_TESTS everything looks good and the output shows the tests pass.  If I add
"REQUIRE(1 == 0);"  and then build RUN_TESTS

It shows the tests failed but then posts a bunch of CTEST errors.  The error list also shows an MSB3073 from Micorosft.Cppcommon.targets.

See Screenshots attached.  I'm wondering if this is unusual, or if this is normal and to be expected.  If took some fussing, but this is now the only unusual behavior in my Dev Environment.  Want to check it out before I start coding in earnest.  If anyone has any thoughts, please let me know.  Thanks!

I've created a new package and I'm examining the HelloWorld object in that package.  Particular looking at how Unit tests work.
By default a

Errors when building RUN_TESTS if tests fail.