Bug 525521 - BlockJUnit4ClassRunner validateConstructor and validateInstanceMethods can't see the @Test annotations
Summary: BlockJUnit4ClassRunner validateConstructor and validateInstanceMethods can't ...
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: webtools.java ee config (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: platform-runtime-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: test
Depends on:
Blocks:
 
Reported: 2017-10-03 12:53 EDT by emillio onken CLA
Modified: 2018-07-16 16:37 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description emillio onken CLA 2017-10-03 12:53:33 EDT 
I can't seem to shake this error. The Eclipse Runner appears to find the @Test annotations however the BlockJUnit4ClassRunner validateConstructor and validateInstanceMethods can't see the @Test annotations.

I've attached a copy of code in git repository reference. bhhc.java throws the exception upon execution.

Supported Data:

SRC: https://github.com/agolem2/MavenJunit/blob/master/src/Test/bhhc.java

ERROR:

Google Completed Test Case bhhc Date: 2017-09-26 08_57_17.318 Test run was NOT successful:

No runnable methods - Trace: java.lang.Exception: No runnable methods
org.junit.runners.BlockJUnit4ClassRunner.validateInstanceMethods(BlockJUnit4Cl
assRunner.java:191)
org.junit.runners.BlockJUnit4ClassRunner.collectInitializationErrors(BlockJUni
t4ClassRunner.java:128)


Test class should have exactly one public constructor - Trace: 
java.lang.Exception: Test class should have exactly one public constructor
org.junit.runners.BlockJUnit4ClassRunner.validateOnlyOneConstructor(BlockJUnit
4ClassRunner.java:158)
org.junit.runners.BlockJUnit4ClassRunner.validateConstructor(BlockJUnit4ClassR
unner.java:147)