Tom,
Thanks sorry. Yes I have specified in my root POM surefire-plugin 2.3 but
not in my submodule one (I will try that right now). The test ource is the
one straight out of the FAQ regarding the colleciton, very simple test,
passes on 3.8.1 but fails when I move up to 4.0 using the surefire plugin.
I'm using Junit-4.0.
Is suppose to work? The surefire report claims there is a null pointer:
Here is my source:
import static org.junit.Assert.*;
import java.util.ArrayList;
import java.util.Collection;
import org.junit.Before;
import org.junit.Test;
public class MyTest {
private Collection<Object> c;
@Before
public void setUp() {
c = new ArrayList<Object>();
}
@Test
public void testSomeMethod() {
assertTrue(c.isEmpty());
}
}
Claims c is null which it isn't provided @Before runs (if I eliminate the
method and put it in my testSomeMethod() it passes. How can I tell what
version of surefire I'm running? The -e just says that test case has
failed, etc stack.
What am I doing wrong? (man, I've used maven2 in all kinds of advanced ways
and I feel retarded that this is not working!).
-aps
On 5/23/07, Tom Huybrechts <[EMAIL PROTECTED]> wrote:
would you mind sharing some more information ? POMs, exceptions, test
source, -X output ?
As a general remark: make sure you have the latest surefire plugin...
Tom
On 5/23/07, Alexander Sack <[EMAIL PROTECTED]> wrote:
> Hey folks, is this a known issue that if I use @Before it will fail my
> test? I searched some of the archives and saw some threads go by about
> this. Is this still an issue?
>
> Thanks!
>
> -aps
>
> --
> "What lies behind us and what lies in front of us is of little concern
to
> what lies within us." -Ralph Waldo Emerson
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
"What lies behind us and what lies in front of us is of little concern to
what lies within us." -Ralph Waldo Emerson
