History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: QB-1325
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Steve Luo
Reporter: Steve Luo
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
QuickBuild

Inconsistencies for skipped tests in JUnit Test

Created: 30/Jul/12 07:11 AM   Updated: 23/Aug/12 06:31 AM
Component/s: None
Affects Version/s: None
Fix Version/s: 4.0.50

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown


 Description  « Hide
I am experimenting with using the JUnit plugin to generate test reports and am noticing some inconsistent behavior in the UI regarding skipped steps.

1) Although the plugin doesn't strictly treat a "skip" as a failure, a newly skipped test shows up as a newly failed test. When clicking on the "New Failed" count, it takes the user to a tag that shows failed tests. But the skipped test doesn't show up there. One must click on the "By Test" link to see the skipped test. That skipped test is in turn linked up, but once again, clicking on it takes the user back to an empty "Failed Tests" tab.

2) If skipped tests are treated in some regard as failures (they count in the "New Failed" counter) they should also be reflected in the "Not Fixed" count.

3) Could the number of skipped steps be made available to go along with the failures and errors? We treat skips as failures and I would like to use it as a condition to fail the step.


 All   Comments   Work Log   Change History      Sort Order:
Change by Steve Luo [30/Jul/12 07:11 AM]
Field Original Value New Value
Assignee Robin Shine [ robinshine ] Steve Luo [ steve ]

Change by Steve Luo [30/Jul/12 08:40 AM]
Summary Inconsistence for skipped tests in JUnit Test Inconsistencies for skipped tests in JUnit Test

Change by Steve Luo [23/Aug/12 06:31 AM]
Status Open [ 1 ] Resolved [ 5 ]
Fix Version/s 4.0.50 [ 11384 ]
Resolution Fixed [ 1 ]