MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0013817CMakeCTestpublic2012-12-27 11:572012-12-27 17:00
ReporterKeith Gardner 
Assigned ToClinton Stimpson 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionno change required 
PlatformOSOS Version
Product VersionCMake 2.8.10.2 
Target VersionFixed in Version 
Summary0013817: Can't export tests to XML without reporting to CDash
DescriptionI would like to be able to export the results of the tests to an XML file with out submitting it to a dashboard. I use TeamCity for my automated regression tests server and it has the ability to load in the XML file exported by CTest. The problem is that I am having build errors when running tests because it is trying to submit the file to a server that does not exist. The executable closes with a non 0 exit code.
Steps To Reproducectest -D Experimental

Don't provide any CTEST_DROP_* information.
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2012-12-27 11:57Keith GardnerNew Issue
2012-12-27 12:18Clinton StimpsonNote Added: 0031946
2012-12-27 12:25Keith GardnerNote Added: 0031947
2012-12-27 13:07Clinton StimpsonNote Added: 0031948
2012-12-27 13:26Keith GardnerNote Added: 0031950
2012-12-27 17:00Clinton StimpsonStatusnew => closed
2012-12-27 17:00Clinton StimpsonAssigned To => Clinton Stimpson
2012-12-27 17:00Clinton StimpsonResolutionopen => no change required

Notes
(0031946)
Clinton Stimpson   
2012-12-27 12:18   
That is already possible with a ctest script.
In the script, just don't call ctest_submit().
(0031947)
Keith Gardner   
2012-12-27 12:25   
Would it be possible to add it without using a ctest script? I define all of my tests within my CMake files.
(0031948)
Clinton Stimpson   
2012-12-27 13:07   
Its also possible to do without a script. Its just that I recommend a script for more advanced usage. And, of course, the tests are still defined in the CMake files.

You can use this command:
ctest -D ExperimentalStart -D ExperimentalUpdate -D ExperimentalConfigure -D ExperimentalBuild -D ExperimentalTest

In case you didn't know, that is essentially equivalent to a script that contains
ctest_start(Experimental)
ctest_update()
ctest_configure()
ctest_build()
ctest_test()

and is executed by
ctest -S my.ctest

I think you already have the capability you need.
(0031950)
Keith Gardner   
2012-12-27 13:26   
Thanks. I didn't understand the capabilities that the command line arguments provided. Sorry for the noise.