AppVeyor: nicely display test results

By producing JUnit output and submitting it to AppVeyor's job processing
we now get some nice display of the tests and their results in the
"Tests" tab.

Author: muggenhor

CMakeLists.txt

@@ -220,6 +220,7 @@ else()
                 DYNAMIC_CPP_STEPS_OBJ=${CUKE_DYNAMIC_CPP_STEPS_OBJ}
                 COMPILE_DYNAMIC_CPP_STEPS=${CUKE_COMPILE_DYNAMIC_CPP_STEPS}
                 CUCUMBER_RUBY=${CUCUMBER_RUBY}
+                --format=junit "--out=${CMAKE_BINARY_DIR}/features"
                 ${ARGN}
                 ${CUKE_FEATURES_DIR}
                 DEPENDS cucumber-cpp

appveyor.yml

@@ -56,6 +56,9 @@ test_script:
 - cmd: cmake --build build --target test
 - cmd: cmake --build build --target features
 
+after_test:
+- cmd: for /r %%v in (TEST-*.xml) do curl -s -F "file=@%%v;filename=%%~nxv" https://ci.appveyor.com/api/testresults/junit/%APPVEYOR_JOB_ID%
+
 notifications:
 - provider: Email
   to:

tests/CMakeLists.txt

@@ -13,8 +13,9 @@ if(GMOCK_FOUND)
         add_executable(${TEST_NAME} ${TEST_FILE}.cpp)
         target_link_libraries(${TEST_NAME} cucumber-cpp-nomain ${CUKE_EXTRA_LIBRARIES} ${ARGN} ${CUKE_GMOCK_LIBRARIES})
         gtest_add_tests(${TEST_NAME} "" ${TEST_FILE}.cpp)
-        # Run all tests in executable at once too. This ensures that the used fixtures get tested properly too.
-        add_test(NAME ${TEST_NAME} COMMAND ${TEST_NAME})
+        # Run all tests in executable at once too. This ensures that the used fixtures get tested
+        # properly too. Additionally gather the output in jUnit compatible output for CI.
+        add_test(NAME ${TEST_NAME} COMMAND ${TEST_NAME} "--gtest_output=xml:TEST-${TEST_NAME}.xml")
     endfunction()
 
     # TODO Compile tests with the least possible code, not with the entire library