Running Qt unit test on gitlab does not show the errors

Running Qt unit test on gitlab does not show the errors

When we run the unit test on Jenkins, we have a detailed output of the error.

[test] FAIL! : Tests::ClientApplicationCrashTest::testCrash(dumpcount < maximum) Compared values are not the same
[test] Actual (dumpCountResult): 1
[test] Expected (dumpCountAfter) : 2
[test] E:\Jenkins\slave_home\workspace\xxx\yyy\ClientApplicationCrashTest.cpp(66) : failure location

The same on gitlab, produces something like:

1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: Der Befehl "setlocal [F:\gitlab\runner\builds\8ede3bbe\0\tnt\client\xxx\build32\tests\RUN_TESTS.vcxproj]
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: “C:\Program Files\CMake\bin\ctest.exe” --force-new-ctest-process -C Release [F:\gitlab\runner\builds\8ede3bbe\0\tnt\client\xxx\build32\tests\RUN_TESTS.vcxproj]
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: if %errorlevel% neq 0 goto :cmEnd [F:\gitlab\runner\builds\8ede3bbe\0\tnt\client\xxx\build32\tests\RUN_TESTS.vcxproj]

that does not help at all.
I set the environment variable CTEST_OUTPUT_ON_FAILURE=1 but it didn’t help.

Any suggestion please?

@mservadei - Thanks for posting!

The Test Summary and Unit Test Report features require junit formatted reports be uploaded (there are some examples on the page) to display.

If those are the places you are looking to see the errors you will need to convert the output and ensure it’s made available with artifact:reports:junit before the data will appear.

I hope this helps, good luck!

-James H, GitLab Product Manager, Verify:Testing