| Key: |
QB-468
|
| Type: |
Bug
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Critical
|
| Assignee: |
Steve Luo
|
| Reporter: |
AlSt
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 26/Nov/09 01:19 PM
Updated: 02/Dec/09 02:23 AM
|
|
| Component/s: |
None
|
| Affects Version/s: |
None
|
| Fix Version/s: |
None
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
File Attachments:
|
None
|
|
Image Attachments:
|
|
|
Environment:
|
PMEase QuickBuild, 2.0.9, 2009-11-23
|
|
|
See attached screenshots: the test case finally fails in {{AbstractManagerInitializerTest.afterClass()}}, that looks like the following and thus is only executed for the whole test class (suite):
{code}
@AfterClass
public static void afterClass() {
{code}
|
|
Description
|
See attached screenshots: the test case finally fails in {{AbstractManagerInitializerTest.afterClass()}}, that looks like the following and thus is only executed for the whole test class (suite):
{code}
@AfterClass
public static void afterClass() {
{code} |
Show » |
| There are no comments yet on this issue.
|
|
Failures in @BeforeClass/@AfterClass in JUnit4 tests are aggregated in junit.framwork package instead of the actual test class (suite)
