| Key: |
QB-1680
|
| Type: |
Improvement
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Minor
|
| Assignee: |
Unassigned
|
| Reporter: |
Justin Georgeson
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 19/Jun/13 01:44 PM
Updated: 21/Jun/13 01:16 PM
|
|
| Component/s: |
None
|
| Affects Version/s: |
5.0.24
|
| Fix Version/s: |
5.0.26
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
We have a Maven/Tycho-based Eclipse RCP build which currently has 90 JUnit report sets, split almost evenly across windows and linux, and this number is going to increase over time. In the current implementation of the Failed Tests gadget I will have to edit the gadget every time a team adds a new unit test bundle. If I could configure wildcards I could set two gadgets, one for "*win64*" and one for "*linux64*" and never have to edit the report selection again.
|
|
Description
|
We have a Maven/Tycho-based Eclipse RCP build which currently has 90 JUnit report sets, split almost evenly across windows and linux, and this number is going to increase over time. In the current implementation of the Failed Tests gadget I will have to edit the gadget every time a team adds a new unit test bundle. If I could configure wildcards I could set two gadgets, one for "*win64*" and one for "*linux64*" and never have to edit the report selection again. |
Show » |
| There are no comments yet on this issue.
|
|
Allow a comma-separated list of report set names with wildcard support for the Failed Tests gadget. 