Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: 2.0.0Release
-
Fix Version/s: None
-
Component/s: Testing, Running, Debugging
-
Labels:
-
Environment:Groovy-Eclipse Feature 2.0.1.20100129-0800-e35
-
Number of attachments :
Description
Choosing the jUnit4 flavor of unit tests produces methods like:
public void setUp() throws Exception {
}
These should be groovied into
void setUp() {
}
Thanks Andrew, for pointing me to this and GRE-639 as something to look at.
I thought to also put the useful pointers you gave in here, for easy reference / record keeping.
Andrew's email:
>
> GRECLIPSE-638
>
GRECLIPSE-639>
> Both deal with the new groovy test case wizard. The solution for both of
> them will either be to override methods from the superclass and use
> reflection to access private fields/methods. Or, if it gets too ugly, you
> can rewrite the new test wizard by copying code from its superclass and
> making all the changes you need.