If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 04/Sep/11 02:29 AM
Updated: 04/Sep/11 02:29 AM
|
|
Component/s: |
None
|
Affects Version/s: |
None
|
Fix Version/s: |
None
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
cppunit can create XML output similar to JUnit XML output, but with different tags and attributes.
Sample cppunit output:
<?xml version="1.0" encoding='ISO-8859-1' standalone='yes' ?>
<TestRun>
<FailedTests>
<FailedTest id="2">
<Name>DatastoreTestFixture::testCreateConnection</Name>
<FailureType>Error</FailureType>
<Message>uncaught exception of unknown type
</Message>
</FailedTest>
</FailedTests>
<SuccessfulTests>
<Test id="1">
<Name>DatastoreTestFixture::testConstructor</Name>
</Test>
<Test id="3">
<Name>DatastoreTestFixture::testGetConnectionStatus</Name>
</Test>
</SuccessfulTests>
<Statistics>
<Tests>3</Tests>
<FailuresTotal>1</FailuresTotal>
<Errors>1</Errors>
<Failures>0</Failures>
</Statistics>
</TestRun>
|
Description
|
cppunit can create XML output similar to JUnit XML output, but with different tags and attributes.
Sample cppunit output:
<?xml version="1.0" encoding='ISO-8859-1' standalone='yes' ?>
<TestRun>
<FailedTests>
<FailedTest id="2">
<Name>DatastoreTestFixture::testCreateConnection</Name>
<FailureType>Error</FailureType>
<Message>uncaught exception of unknown type
</Message>
</FailedTest>
</FailedTests>
<SuccessfulTests>
<Test id="1">
<Name>DatastoreTestFixture::testConstructor</Name>
</Test>
<Test id="3">
<Name>DatastoreTestFixture::testGetConnectionStatus</Name>
</Test>
</SuccessfulTests>
<Statistics>
<Tests>3</Tests>
<FailuresTotal>1</FailuresTotal>
<Errors>1</Errors>
<Failures>0</Failures>
</Statistics>
</TestRun>
|
Show » |
There are no comments yet on this issue.
|
|