Make ctest spit out xml file (without dashboard)

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Make ctest spit out xml file (without dashboard)

Eric Noulard
Hi there,

Is it possible to make ctest spit out its result in an xml formatted file without
sending it to some dashboard. ?

I only need something xml-parsable ctest output locally.

--
Eric

--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake
Reply | Threaded
Open this post in threaded view
|

Re: Make ctest spit out xml file (without dashboard)

Craig Scott-3


On Mon, Mar 19, 2018 at 10:39 PM, Eric Noulard <[hidden email]> wrote:
Hi there,

Is it possible to make ctest spit out its result in an xml formatted file without
sending it to some dashboard. ?

Yes, you can control the individual steps of a full dashboard run and just leave out the submit step. For example:

ctest -T Start -T Update -T Configure -T Build -T Test -T Coverage -T MemCheck

Leave out any of the above -T actions you don't need. XML result files will be in a Testing/YYYYMMDD-hhmm directory and log files in Testing/Temporary. The Start action creates a new YYYYMMDD-hhmm timestamp directory that the rest of the steps will then store their XML result files in. The first line of the file at Testing/TAG records that timestamp and the second line in there you won't care about if not submitting the results to a dashboard.

Hopefully that gets you far enough along to what you need.

 

I only need something xml-parsable ctest output locally.

--
Eric

--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake




--
Craig Scott
Melbourne, Australia

--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake
Reply | Threaded
Open this post in threaded view
|

Re: Make ctest spit out xml file (without dashboard)

Eric Noulard


2018-03-19 13:14 GMT+01:00 Craig Scott <[hidden email]>:


On Mon, Mar 19, 2018 at 10:39 PM, Eric Noulard <[hidden email]> wrote:
Hi there,

Is it possible to make ctest spit out its result in an xml formatted file without
sending it to some dashboard. ?

Yes, you can control the individual steps of a full dashboard run and just leave out the submit step. For example:

ctest -T Start -T Update -T Configure -T Build -T Test -T Coverage -T MemCheck

Leave out any of the above -T actions you don't need. XML result files will be in a Testing/YYYYMMDD-hhmm directory and log files in Testing/Temporary. The Start action creates a new YYYYMMDD-hhmm timestamp directory that the rest of the steps will then store their XML result files in. The first line of the file at Testing/TAG records that timestamp and the second line in there you won't care about if not submitting the results to a dashboard.

Hopefully that gets you far enough along to what you need.

This is indeed far just enough for my needs.
Thank you very much Craig. 


--
Eric

--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake