[CMake] CTest: Any way around the "one test == one program invocation" assumption?

[Philip Lowman]

On Tue, Jun 8, 2010 at 4:32 AM, Chris Hillery <chillery-cmake at lambda.nu>wrote:

> On Tue, Jun 8, 2010 at 1:00 AM, Biddiscombe, John A. <biddisco at cscs.ch>wrote:
>
>> I'm sure someone has a better answer ... but ...
>>
>> > I have complete control over the test
>> > program and can make it output whatever I want.
>>
>> Have a look at the XML produced by ctest itself and generate it yourself?
>> then submit it and you should see each test separately
>>
>> (Just thinking out loud)
>>
>
> Yeah, worst case I'll head down that path. It's a hairy path though. For
> instance, I'd still definitely want to run "normal" ctest tests as well,
> which means the XML would need to be merged in some fashion. Also, it seems
> like doing it that way opens you up to possible problems later if ctest or
> cdash change the XML format at all.
>
> All in all it'd be much nicer if there was some kind of hook in ctest which
> could be used to inform it that a number of tests had been run, and let it
> populate and submit the XML report based on that information. But, if
> there's any way to do that, it's highly undocumented...
>

It doesn't appear like there is a class for storing the test results before
serializing the XML document to a file.  Sounds like that's what would have
to be written.

cmCTestTestHandler::GenerateDartOutput
Looks like it may be a place to start?

-- 
Philip Lowman
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20100608/1238eba1/attachment.htm>