It's all about the answers!

Ask a question

Build failing posting results of cppunitLogPublisher


Mitchell Packer (111) | asked Jul 19 '11, 8:59 a.m.
When we run our cpp unit tests it creates a xml file which we can find to have no problems however when we try and publish it fails with the following error.

Publishing JUnit log "C:\TCSources\ANT_Workspace\Runtime\deploy\win32\Debug\UnitTestResults.xml".
java.lang.StringIndexOutOfBoundsException
at java.lang.String.substring(String.java:1088)
at com.ibm.team.build.internal.toolkit.cppunit.CppUnitParser.endElement(CppUnitParser.java:176)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at com.ibm.team.build.internal.toolkit.unit.UnitParser.parse(UnitParser.java:54)
at com.ibm.team.build.internal.toolkit.cppunit.CppUnitParser.parse(CppUnitParser.java:85)
at com.ibm.team.build.internal.toolkit.unit.UnitLogParser.parse(UnitLogParser.java:77)
at com.ibm.team.build.internal.toolkit.unit.UnitLogParser.parse(UnitLogParser.java:66)
at com.ibm.team.build.internal.toolkit.unit.UnitLogPublisher.publishFile(UnitLogPublisher.java:222)
at com.ibm.team.build.internal.toolkit.unit.UnitLogPublisher.publish(UnitLogPublisher.java:180)
at com.ibm.team.build.ant.task.UnitLogPublisherTask.updateBuildResult(UnitLogPublisherTask.java:131)
at com.ibm.team.build.ant.task.AbstractPublisherTask.doExecute(AbstractPublisherTask.java:105)
at com.ibm.team.build.ant.task.AbstractTeamBuildTask.execute(AbstractTeamBuildTask.java:653)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
at org.apache.tools.ant.Main.runBuild(Main.java:758)
at org.apache.tools.ant.Main.startAnt(Main.java:217)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)

7 answers



permanent link
Brent Ulbricht (2.5k11) | answered Jul 19 '11, 9:54 a.m.
JAZZ DEVELOPER
When we run our cpp unit tests it creates a xml file which we can find to have no problems however when we try and publish it fails with the following error.

Publishing JUnit log "C:\TCSources\ANT_Workspace\Runtime\deploy\win32\Debug\UnitTestResults.xml".
java.lang.StringIndexOutOfBoundsException
at java.lang.String.substring(String.java:1088)
at com.ibm.team.build.internal.toolkit.cppunit.CppUnitParser.endElement(CppUnitParser.java:176)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at com.ibm.team.build.internal.toolkit.unit.UnitParser.parse(UnitParser.java:54)
at com.ibm.team.build.internal.toolkit.cppunit.CppUnitParser.parse(CppUnitParser.java:85)
at com.ibm.team.build.internal.toolkit.unit.UnitLogParser.parse(UnitLogParser.java:77)
at com.ibm.team.build.internal.toolkit.unit.UnitLogParser.parse(UnitLogParser.java:66)
at com.ibm.team.build.internal.toolkit.unit.UnitLogPublisher.publishFile(UnitLogPublisher.java:222)
at com.ibm.team.build.internal.toolkit.unit.UnitLogPublisher.publish(UnitLogPublisher.java:180)
at com.ibm.team.build.ant.task.UnitLogPublisherTask.updateBuildResult(UnitLogPublisherTask.java:131)
at com.ibm.team.build.ant.task.AbstractPublisherTask.doExecute(AbstractPublisherTask.java:105)
at com.ibm.team.build.ant.task.AbstractTeamBuildTask.execute(AbstractTeamBuildTask.java:653)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
at org.apache.tools.ant.Main.runBuild(Main.java:758)
at org.apache.tools.ant.Main.startAnt(Main.java:217)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)


Hi,

That's around the area where it tries to derive the test name and test class name. What version of RTC and CppUnit are you using? If you could copy/paste the XML file (you'd have to check the 'Disable HTML in the post') here or open a work item and attach that would allow for getting a better look.

Brent Ulbricht
RTC Build Lead

permanent link
Mitchell Packer (111) | answered Jul 19 '11, 10:37 a.m.
When we run our cpp unit tests it creates a xml file which we can find to have no problems however when we try and publish it fails with the following error.

Publishing JUnit log "C:\TCSources\ANT_Workspace\Runtime\deploy\win32\Debug\UnitTestResults.xml".
java.lang.StringIndexOutOfBoundsException
at java.lang.String.substring(String.java:1088)
at com.ibm.team.build.internal.toolkit.cppunit.CppUnitParser.endElement(CppUnitParser.java:176)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at com.ibm.team.build.internal.toolkit.unit.UnitParser.parse(UnitParser.java:54)
at com.ibm.team.build.internal.toolkit.cppunit.CppUnitParser.parse(CppUnitParser.java:85)
at com.ibm.team.build.internal.toolkit.unit.UnitLogParser.parse(UnitLogParser.java:77)
at com.ibm.team.build.internal.toolkit.unit.UnitLogParser.parse(UnitLogParser.java:66)
at com.ibm.team.build.internal.toolkit.unit.UnitLogPublisher.publishFile(UnitLogPublisher.java:222)
at com.ibm.team.build.internal.toolkit.unit.UnitLogPublisher.publish(UnitLogPublisher.java:180)
at com.ibm.team.build.ant.task.UnitLogPublisherTask.updateBuildResult(UnitLogPublisherTask.java:131)
at com.ibm.team.build.ant.task.AbstractPublisherTask.doExecute(AbstractPublisherTask.java:105)
at com.ibm.team.build.ant.task.AbstractTeamBuildTask.execute(AbstractTeamBuildTask.java:653)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
at org.apache.tools.ant.Main.runBuild(Main.java:758)
at org.apache.tools.ant.Main.startAnt(Main.java:217)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)


Hi,

That's around the area where it tries to derive the test name and test class name. What version of RTC and CppUnit are you using? If you could copy/paste the XML file (you'd have to check the 'Disable HTML in the post') here or open a work item and attach that would allow for getting a better look.

Brent Ulbricht
RTC Build Lead

We are using cppunit-1.12.1 and the team concert 3.0 Ifix1 Below is the xml file is

<xml>
<TestRun>
<FailedTests></FailedTests>
<SuccessfulTests>
<Test>
<Name>Siemens::UnitTest::AdrComponentTest::TestAdrComponent_A</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::AdrComponentTest::TestAdrComponent_B</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::AdrComponentTest::TestAdrComponent_C</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::AdrComponentTest::TestAdrComponent_D</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::AdrComponentTest::TestAdrComponent_E</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::DataFactoryTest::AddReferenceTest</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::DataFactoryTest::UniqueTypesByNameThrowTest</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::DrasPollingUnitTest::DrasPolling_TestA</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::DrasPollingUnitTest::DrasPolling_TestB</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::NormalizerComponentTest::NoEventTest_A</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::NormalizerComponentTest::EventWithStartTimeNowTest_B</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::NormalizerComponentTest::EventWithStartTimeAndEndTimeBeforeNowTest_C</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::NormalizerComponentTest::EventWithStartTimeBeforeNowAndEndTimeAfterNowTest_D</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::NormalizerComponentTest::UpdateExistingFutureEventTest_E</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::NormalizerComponentTest::UpdateExistingOngoingEventTest_F</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::NormalizerComponentTest::CancelFutureEventTest_G</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::NormalizerComponentTest::CancelOngoingEventTest_H</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::ResolverTest::TestResolver_A</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::ResolverTest::TestResolver_B</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::ResolverTest::TestResolver_C</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::ResolverTest::TestResolver_D</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::ResolverTest::TestResolver_E</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::SDRTest::BasicTest</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::SDRTest::SDRAssociation1</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::SDRTest::SDRAssociation2</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::SDRTest::SDRAssociation3</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::SDRTest::SDRAssociation4</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::SDRTest::BasicTest2</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::TypeEventQueueTest::HowToUseDemoTest</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::TypeEventQueueTest::AddSubscriptionTest</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::TypeEventQueueTest::AddSameCallbackTest</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::TypeEventQueueTest::ProcessEventsTest</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::TypeTest::testConstructor</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::TypeTest::testAddProperty</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::XmlDataObjectsImportTest::HowToUseDemoTest</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::XmlDataObjectsImportTest::MissingDataObjectNameTest</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::XmlDataObjectsImportTest::PropertyAsXmlAttributeTest</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::XmlDataObjectsImportTest::PropertyAsXmlElementTest</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::XmlDataObjectsImportTest::OneToOneReferenceTest</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::XmlDataObjectsImportTest::OneToManyReferenceTest</Name>
</Test>
<Test>
<Name>Siemens::UnitTest::XmlDataObjectsImportTest::MergeSimplePropertyTest</Name>
</Test>
</SuccessfulTests>
<Statistics>
<Tests>41</Tests>
<FailuresTotal>0</FailuresTotal>
<Errors>0</Errors>
<Failures>0</Failures>
</Statistics>
</TestRun>

permanent link
Brent Ulbricht (2.5k11) | answered Jul 19 '11, 12:08 p.m.
JAZZ DEVELOPER
Hi,

I ran with the pasted XML file and did not get the exception you received but another one because the 'id' attribute is missing on the 'Test' element.

java.lang.NumberFormatException: null
at java.lang.Integer.parseInt(Integer.java:449)
at java.lang.Integer.parseInt(Integer.java:531)
at com.ibm.team.build.internal.toolkit.cppunit.CppUnitParser.startElement(CppUnitParser.java:105)

In the CppUnit logs that I've seen there is an 'id' like the one shown below.


<SuccessfulTests>
<Test>
<Name>MyTest::testOne</Name>
</Test>
</SuccessfulTests>


Brent Ulbricht
RTC Build Lead

permanent link
Mitchell Packer (111) | answered Jul 19 '11, 12:56 p.m.
Hi,

I ran with the pasted XML file and did not get the exception you received but another one because the 'id' attribute is missing on the 'Test' element.

java.lang.NumberFormatException: null
at java.lang.Integer.parseInt(Integer.java:449)
at java.lang.Integer.parseInt(Integer.java:531)
at com.ibm.team.build.internal.toolkit.cppunit.CppUnitParser.startElement(CppUnitParser.java:105)

In the CppUnit logs that I've seen there is an 'id' like the one shown below.


<SuccessfulTests>
<Test>
<Name>MyTest::testOne</Name>
</Test>
</SuccessfulTests>


Brent Ulbricht
RTC Build Lead


I double checked the code and still not sure this is the complete code. Sorry I'm not use to writing in forums



<?xml version="1.0" encoding='ISO-8859-1' standalone='yes' ?>
<TestRun>
<FailedTests></FailedTests>
<SuccessfulTests>
<Test id="1">
<Name>Siemens::UnitTest::AdrComponentTest::TestAdrComponent_A</Name>
</Test>
<Test id="2">
<Name>Siemens::UnitTest::AdrComponentTest::TestAdrComponent_B</Name>
</Test>
<Test id="3">
<Name>Siemens::UnitTest::AdrComponentTest::TestAdrComponent_C</Name>
</Test>
<Test id="4">
<Name>Siemens::UnitTest::AdrComponentTest::TestAdrComponent_D</Name>
</Test>
<Test id="5">
<Name>Siemens::UnitTest::AdrComponentTest::TestAdrComponent_E</Name>
</Test>
<Test id="6">
<Name>Siemens::UnitTest::DataFactoryTest::AddReferenceTest</Name>
</Test>
<Test id="7">
<Name>Siemens::UnitTest::DataFactoryTest::UniqueTypesByNameThrowTest</Name>
</Test>
<Test id="8">
<Name>Siemens::UnitTest::DrasPollingUnitTest::DrasPolling_TestA</Name>
</Test>
<Test id="9">
<Name>Siemens::UnitTest::DrasPollingUnitTest::DrasPolling_TestB</Name>
</Test>
<Test id="10">
<Name>Siemens::UnitTest::NormalizerComponentTest::NoEventTest_A</Name>
</Test>
<Test id="11">
<Name>Siemens::UnitTest::NormalizerComponentTest::EventWithStartTimeNowTest_B</Name>
</Test>
<Test id="12">
<Name>Siemens::UnitTest::NormalizerComponentTest::EventWithStartTimeAndEndTimeBeforeNowTest_C</Name>
</Test>
<Test id="13">
<Name>Siemens::UnitTest::NormalizerComponentTest::EventWithStartTimeBeforeNowAndEndTimeAfterNowTest_D</Name>
</Test>
<Test id="14">
<Name>Siemens::UnitTest::NormalizerComponentTest::UpdateExistingFutureEventTest_E</Name>
</Test>
<Test id="15">
<Name>Siemens::UnitTest::NormalizerComponentTest::UpdateExistingOngoingEventTest_F</Name>
</Test>
<Test id="16">
<Name>Siemens::UnitTest::NormalizerComponentTest::CancelFutureEventTest_G</Name>
</Test>
<Test id="17">
<Name>Siemens::UnitTest::NormalizerComponentTest::CancelOngoingEventTest_H</Name>
</Test>
<Test id="18">
<Name>Siemens::UnitTest::ResolverTest::TestResolver_A</Name>
</Test>
<Test id="19">
<Name>Siemens::UnitTest::ResolverTest::TestResolver_B</Name>
</Test>
<Test id="20">
<Name>Siemens::UnitTest::ResolverTest::TestResolver_C</Name>
</Test>
<Test id="21">
<Name>Siemens::UnitTest::ResolverTest::TestResolver_D</Name>
</Test>
<Test id="22">
<Name>Siemens::UnitTest::ResolverTest::TestResolver_E</Name>
</Test>
<Test id="23">
<Name>Siemens::UnitTest::SDRTest::BasicTest</Name>
</Test>
<Test id="24">
<Name>Siemens::UnitTest::SDRTest::SDRAssociation1</Name>
</Test>
<Test id="25">
<Name>Siemens::UnitTest::SDRTest::SDRAssociation2</Name>
</Test>
<Test id="26">
<Name>Siemens::UnitTest::SDRTest::SDRAssociation3</Name>
</Test>
<Test id="27">
<Name>Siemens::UnitTest::SDRTest::SDRAssociation4</Name>
</Test>
<Test id="28">
<Name>Siemens::UnitTest::SDRTest::BasicTest2</Name>
</Test>
<Test id="29">
<Name>Siemens::UnitTest::TypeEventQueueTest::HowToUseDemoTest</Name>
</Test>
<Test id="30">
<Name>Siemens::UnitTest::TypeEventQueueTest::AddSubscriptionTest</Name>
</Test>
<Test id="31">
<Name>Siemens::UnitTest::TypeEventQueueTest::AddSameCallbackTest</Name>
</Test>
<Test id="32">
<Name>Siemens::UnitTest::TypeEventQueueTest::ProcessEventsTest</Name>
</Test>
<Test id="33">
<Name>Siemens::UnitTest::TypeTest::testConstructor</Name>
</Test>
<Test id="34">
<Name>Siemens::UnitTest::TypeTest::testAddProperty</Name>
</Test>
<Test id="35">
<Name>Siemens::UnitTest::XmlDataObjectsImportTest::HowToUseDemoTest</Name>
</Test>
<Test id="36">
<Name>Siemens::UnitTest::XmlDataObjectsImportTest::MissingDataObjectNameTest</Name>
</Test>
<Test id="37">
<Name>Siemens::UnitTest::XmlDataObjectsImportTest::PropertyAsXmlAttributeTest</Name>
</Test>
<Test id="38">
<Name>Siemens::UnitTest::XmlDataObjectsImportTest::PropertyAsXmlElementTest</Name>
</Test>
<Test id="39">
<Name>Siemens::UnitTest::XmlDataObjectsImportTest::OneToOneReferenceTest</Name>
</Test>
<Test id="40">
<Name>Siemens::UnitTest::XmlDataObjectsImportTest::OneToManyReferenceTest</Name>
</Test>
<Test id="41">
<Name>Siemens::UnitTest::XmlDataObjectsImportTest::MergeSimplePropertyTest</Name>
</Test>
</SuccessfulTests>
<Statistics>
<Tests>41</Tests>
<FailuresTotal>0</FailuresTotal>
<Errors>0</Errors>
<Failures>0</Failures>
</Statistics>
</TestRun>

permanent link
Brent Ulbricht (2.5k11) | answered Jul 19 '11, 3:17 p.m.
JAZZ DEVELOPER
Hi,

Thanks for the log. I was able to recreate your exception and have filed a defect for the problem. In the example log you pasted, it's getting caught on 'Siemens::UnitTest::XmlDataObjectsImportTest::MissingDataObjectNameTest' in my tests, but that's not to say that it might get caught on another one.

Brent Ulbricht
RTC Build Lead

permanent link
Florian Ersch (6) | answered Jul 19 '11, 3:37 p.m.
Thanks for the investigation. Do you have a workaround for us so we can continue to use the Unit Test feature?

Thanks
Florian

permanent link
Brent Ulbricht (2.5k11) | answered Jul 19 '11, 4:41 p.m.
JAZZ DEVELOPER
Thanks for the investigation. Do you have a workaround for us so we can continue to use the Unit Test feature?

Thanks
Florian


The one that I can think of right now is to use a XSLT to transform the CppUnit log file into a JUnit log format and use the junitLogPublisher Ant task . I noticed that this changelog page for CppUnit has mention of a XSLT that can do this transform.

Brent Ulbricht
RTC Build Lead

Your answer


Register or to post 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.