[#QB-468] Failures in @BeforeClass/@AfterClass in JUnit4 tests are aggregated in junit.framwork package instead of the actual test class (suite)

QuickBuild

Failures in @BeforeClass/@AfterClass in JUnit4 tests are aggregated in junit.framwork package instead of the actual test class (suite)

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:

1. screenshot-1.jpg
(296 kb)

2. screenshot-2.jpg
(141 kb)

3. screenshot-3.jpg
(180 kb)

Environment:

PMEase QuickBuild, 2.0.9, 2009-11-23

Description

« Hide

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}

All

Comments

Work Log

Change History

Sort Order:

Change by AlSt [26/Nov/09 01:19 PM]
Field	Original Value	New Value
Attachment		screenshot-1.jpg [ 10122 ]

Change by AlSt [26/Nov/09 01:20 PM]
Attachment		screenshot-2.jpg [ 10123 ]

Change by AlSt [26/Nov/09 01:20 PM]
Attachment		screenshot-3.jpg [ 10124 ]

Change by Robin Shen [26/Nov/09 01:25 PM]
Assignee	Robin Shine [ robinshine ]	Steve Luo [ steve ]

Change by AlSt [26/Nov/09 03:24 PM]
Attachment		TEST-com.dynatrace.diagnostics.communication.tcp.connection.ConnectionManagerTest.xml [ 10125 ]

Change by Steve Luo [26/Nov/09 03:55 PM]
Attachment	TEST-com.dynatrace.diagnostics.communication.tcp.connection.ConnectionManagerTest.xml [ 10125 ]

Change by Robin Shen [02/Dec/09 02:23 AM]
Status	Open [ 1 ]	Resolved [ 5 ]
Resolution		Fixed [ 1 ]