I thought this is a common issue for unit testing. Nobody here had ever done
this before?
Wayne Fay wrote:
>
> This is probably something the junit guys would be able to help you
> with more than we can. Unless of course they say it is strictly a
> Maven/Surefire issue...
>
> Wayne
>
> On 8/
This is probably something the junit guys would be able to help you
with more than we can. Unless of course they say it is strictly a
Maven/Surefire issue...
Wayne
On 8/22/07, flyingtiger <[EMAIL PROTECTED]> wrote:
>
> I don't think there's a way to exclude the Wrapper since it is an inner
> clas
I don't think there's a way to exclude the Wrapper since it is an inner
class. I tried to exclude it but it won't work. I then added a fake test so
the Wrapper class turns to be
public static class Wrapper extends TestSetup {
public Wrapper(){}
I think what you want to do is add the Wrapper class to your list of
excluded files.
**/Wrapper
or something like that. The static inner class is throwing me off,
but you get the idea. At this point, surefire is instantiating it just
fine, but can't find any testXXX methods, so fails t
I changed the inner class to
public static class Wrapper extends TestSetup {
public Wrapper(){
;
}
public Wrapper(Test arg0) {
super(arg0);
//
>> with mvn test I got error
"junit.framework.AssertionFailedError: Class Order$OrderChargeTest has
no
public constructor TestCase(String name) or TestCase()" <<
If memory serves, I think the solution is to make sure all your classes
(inner included) have a no-args constructor (or, as appropriate,
