| << Back to previous view |
|
[QB-468] Failures in @BeforeClass/@AfterClass in JUnit4 tests are aggregated in junit.framwork package instead of the actual test class (suite)
|
|
| Status: | Resolved |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical |
| Reporter: | AlSt | Assigned To: | Steve Luo |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Environment: | PMEase QuickBuild, 2.0.9, 2009-11-23 | ||
| File Attachments: |
screenshot-1.jpg
screenshot-2.jpg
screenshot-3.jpg
|
| 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} |