Key: |
QB-743
|
Type: |
Improvement
|
Status: |
Resolved
|
Resolution: |
Fixed
|
Priority: |
Major
|
Assignee: |
Unassigned
|
Reporter: |
Steve Luo
|
Votes: |
0
|
Watchers: |
0
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 18/Nov/10 09:28 PM
Updated: 21/Nov/10 12:36 AM
|
|
Component/s: |
None
|
Affects Version/s: |
None
|
Fix Version/s: |
3.1.3
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
By default, JUnit report only contains testsuite level system out/error messages, for example:
<testsuite tests="2" errors="1" failures="1" name="regression.DOA">
<properties>
<!-- Not used by QuickBuild -->
</properties>
<testcase classname="regression.DOA.test" name="testFoo1" time="0.30">
</testcase>
<testcase classname="regression.DOA.test" name="testFoo2" time="12.30" >
<failure message="some failure message" type="some failure type">Detailed failure message</failure>
</testcase>
<testcase classname="regression.DOA.test" name="testFoo3" time="12.30" >
<error message="some error message" type="some error type">Detailed error message</error>
</testcase>
<system-out>System out message</system-out>
</testsuite>
while sometimes it maybe more reasonable to place system out/error messages in class level, like:
<testsuite tests="3" errors="1" failures="1" name="regression.DOA">
<properties>
<!-- Not used by QuickBuild -->
</properties>
<testcase classname="regression.DOA.test" name="testFoo1" time="0.30">
<system-out>System out message from testFoo1</system-out>
</testcase>
<testcase classname="regression.DOA.test" name="testFoo2" time="12.30" >
<failure message="some failure message" type="some failure type">Detailed failure message</failure>
<system-out>System out message from testFoo2</system-out>
<system-err>System out message</system-err>
</testcase>
<testcase classname="regression.DOA.test" name="testFoo3" time="12.30" >
<error message="some error message" type="some error type">Detailed error message</error>
<system-err>System out message from testFoo3</system-err>
</testcase>
</testsuite>
It would be nice if QuickBuild is able to handle such case.
|
Description
|
By default, JUnit report only contains testsuite level system out/error messages, for example:
<testsuite tests="2" errors="1" failures="1" name="regression.DOA">
<properties>
<!-- Not used by QuickBuild -->
</properties>
<testcase classname="regression.DOA.test" name="testFoo1" time="0.30">
</testcase>
<testcase classname="regression.DOA.test" name="testFoo2" time="12.30" >
<failure message="some failure message" type="some failure type">Detailed failure message</failure>
</testcase>
<testcase classname="regression.DOA.test" name="testFoo3" time="12.30" >
<error message="some error message" type="some error type">Detailed error message</error>
</testcase>
<system-out>System out message</system-out>
</testsuite>
while sometimes it maybe more reasonable to place system out/error messages in class level, like:
<testsuite tests="3" errors="1" failures="1" name="regression.DOA">
<properties>
<!-- Not used by QuickBuild -->
</properties>
<testcase classname="regression.DOA.test" name="testFoo1" time="0.30">
<system-out>System out message from testFoo1</system-out>
</testcase>
<testcase classname="regression.DOA.test" name="testFoo2" time="12.30" >
<failure message="some failure message" type="some failure type">Detailed failure message</failure>
<system-out>System out message from testFoo2</system-out>
<system-err>System out message</system-err>
</testcase>
<testcase classname="regression.DOA.test" name="testFoo3" time="12.30" >
<error message="some error message" type="some error type">Detailed error message</error>
<system-err>System out message from testFoo3</system-err>
</testcase>
</testsuite>
It would be nice if QuickBuild is able to handle such case. |
Show » |
There are no comments yet on this issue.
|
|