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?





Alternatively, how about making the custom test return a simple XML which had

<test 1>

  name

  pass/fail

  < full test text output>

/>

<test 2>

  name

  pass/fail

  <full test text output>

/>

... /etc/etc

and then add a function into cmCtestHandler to parse the result - in the fixed 
form you define - back into a standard Dart compatible form which it then 
submits as usual. A slight modification of ADD_TEST to trigger the new form of 
output would probably be enough.



JB


_______________________________________________
Powered by www.kitware.com

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

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

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

Reply via email to