RTC Reports
Hi,
I'm running a build in RTC that runs Rhapsody ,VectorCast and Lint. The problem is that i can't find a way to create a report that shows me the xml output that was created during the build by VectorCast and Lint. What do i need to do? do i need to install somehting for it? Thank you, Galit. |
8 answers
Hi Galit,
With base RTC Build, we support various test frameworks: JUnit, MSTest, CPPTest and NUnit. I'm not aware of any RTC extensions directly supporting the other tools you mention. You can use the logPublisher Ant task to publish the XML file to the build result. If you're able to determine the overall success/failure status based on the log, that can be specified when uploading the log, which will be reflected in the overall build status. Another option is to use XSLT to transform the log files into the form we expect for JUnit or one of the other supported tools. For example, see: http://jazz.net/forums/viewtopic.php?t=9173 |
|
Hi,
I'm running RTC build not with ant commands, but with command line that runs a Final Builder project (in the project i'm running Rhapsody , VectorCast and Lint). When finishing the build in the artifact directory i'm getting xml outputs from VectorCast and Lint. I'm sorry but i still don't understand how can i create a report out of these outputs? Thank you, Galit Levin. |
|
Can you post an example XML file from one of these tools? We could help craft an XSLT to transform it into a format we support. Be sure to check 'Disable HTML in this post' or the forum software will lose the content between tags (also note that this setting gets lost if you use Preview).
The Ant tasks to publish the data could be invoked from your command line script, which we could help with too. |
|
Hi,
I posted an example of VectorCast output. I want to present in the report the contents of TestCaseHtmlFile and totalpass. It will be great if you can show me how to publish the data from command line. Thank you, Galit Levin. <?xml version="1.0" encoding="UTF-8" ?> - <testcase_data xml_testcase_version="1.0"> <Share>\\COMPUTER_NAME\Builds\Project2\2010\05\16_164048\Calculator2Multiply\CALCULATOR_management_report.html</Share> <Share1>\\COMPUTER_NAME\Builds\Project2\2010\05\16_164048\Calculator2Multiply\CALCULATOR_management_report.html</Share1> <TestCaseHtmlFile>CALCULATOR_management_report.html</TestCaseHtmlFile> <totalpass>1 / 1</totalpass> - <compound> <name><<COMPOUND>></name> </compound> - <init> <name><<INIT>></name> </init> - <unit index="9" coverage_type="STATEMENT"> <name>Calculator</name> - <subprogram index="1"> <name>(cl)Calculator::Calculator</name> </subprogram> - <subprogram index="2"> <name>(cl)Calculator::~Calculator</name> </subprogram> - <subprogram index="3"> <name>(cl)Calculator::Multiply</name> - <testcase index="1"> <name>(CL)CALCULATOR::MULTIPLY.001</name> <command_file>C-000001.DAT</command_file> - <creation_date> <month>5</month> <day>16</day> <year>2010</year> </creation_date> - <creation_time> <hour>4</hour> <minute>41</minute> <seconds>50</seconds> <ampm>PM</ampm> </creation_time> - <execution_date> <month>5</month> <day>16</day> <year>2010</year> </execution_date> - <execution_time> <hour>4</hour> <minute>41</minute> <seconds>51</seconds> <ampm>PM</ampm> </execution_time> - <results> <pass>1</pass> <total>1</total> </results> </testcase> </subprogram> </unit> </testcase_data> |
|
Thanks, Galit, we'll have a look. Do you have an example where tests are failing (preferable), or can you describe how failures are expressed in the XML?
|
|
Hi,
Failures are expressed in the XML under the "totalpass" tab. If the result is 0/0 or X/Y while X<Y then this is a failure. Thank you, Galit Levin. |
|
Is that also true for individual test cases, e.g. would a test case failure be expressed as:
In the event of a failure, does the testcase carry extra information, such as the stack trace at the point of failure? If so, how is this represented? |
|
Hi,
The only way that failures are expressed is under the "totalpass" tab, and there is no extra information. Thank you, Galit Levin. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.