| Key: |
CCNET-704
|
| Type: |
Improvement
|
| Status: |
Open
|
| Priority: |
Minor
|
| Assignee: |
Unassigned
|
| Reporter: |
Grant Drake
|
| Votes: |
0
|
| Watchers: |
1
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
|
| Component/s: |
Stylesheet
|
| Affects Version/s: |
None
|
| Fix Version/s: |
None
|
|
|
Original Estimate:
|
5 minutes
|
Remaining Estimate:
|
5 minutes
|
Time Spent:
|
Unknown
|
|
File Attachments:
|
1.
unittests.xsl (13 kb)
2.
unittests_1.1.xsl (10 kb)
|
|
|
We noticed a problem whereby failures in the test fixture teardown are not reported on the front page build report - you see that
nunit-console has failed on the build report page but you can only actually see why by sifting through the NAnt output.
The solution is a tweak to unittests.xsl, so that it looks for //test-suite/failure nodes, which is where
the necessary messages can be found. I have taken the simplest route of adding a
"Suite failures" message at the top (only displayed if there are any), and listing any failures in the same
area as unit test failures.
|
|
Description
|
We noticed a problem whereby failures in the test fixture teardown are not reported on the front page build report - you see that
nunit-console has failed on the build report page but you can only actually see why by sifting through the NAnt output.
The solution is a tweak to unittests.xsl, so that it looks for //test-suite/failure nodes, which is where
the necessary messages can be found. I have taken the simplest route of adding a
"Suite failures" message at the top (only displayed if there are any), and listing any failures in the same
area as unit test failures. |
Show » |
|
Improved build summary stylesheet to show test fixture setup/teardown failures