> I think you don't get the point. By detection we mean that given a base
> directory, Surefire will find all test classes beneath it, w/o us having to
> adhere to any naming convention. Surefire can't do this.
I agree with one small edit -- Surefire can't do this *today*. If this
is important eno
John Stoneham wrote:
>
> To be clearer - surefire will certainly detect JUnit 4 tests
>
I think you don't get the point. By detection we mean that given a base
directory, Surefire will find all test classes beneath it, w/o us having to
adhere to any naming convention. Surefire can't do this.
On Mon, Dec 15, 2008 at 11:12 AM, Peter Niederwieser wrote:
>> What you are saying is that the surefire plugin is not JUnit4 enabled?
>
> Unfortunately, Surefire isn't capable of detecting JUnit 4 tests by itself.
> You always have to adhere to some naming convention.
To be clearer - surefire wil
CheapLisa wrote:
>
> What you are saying is that the surefire plugin is not JUnit4 enabled?
>
Unfortunately, Surefire isn't capable of detecting JUnit 4 tests by itself.
You always have to adhere to some naming convention.
Cheers,
Peter
--
View this message in context:
http://www.nabble.com
not necessarily endorse content contained within
> > this transmission.
> >
> >
> >
> >
> >> Date: Wed, 10 Dec 2008 12:44:45 -0800
> >> From: l...@purpleblade.net
> >> To: users@maven.apache.org
> >> Subject: Re: Is Maven / JUnit
t; Sender does not endorse distribution to any party other than intended
> recipient. Sender does not necessarily endorse content contained within
> this transmission.
>
>
>
>
>> Date: Wed, 10 Dec 2008 12:44:45 -0800
>> From: l...@purpleblade.net
>> To: user
lity note
>>> > Everything in this e-mail and any attachments relates to the official
>>> > business of Sender. This transmission is of a confidential nature and
>>> > Sender does not endorse distribution to any party other than intended
>>> > recipien
f Sender. This transmission is of a confidential nature and
>> > Sender does not endorse distribution to any party other than intended
>> > recipient. Sender does not necessarily endorse content contained within
>> > this transmission.
>> >
>> >
>> >
attachments relates to the official
> > business of Sender. This transmission is of a confidential nature and
> > Sender does not endorse distribution to any party other than intended
> > recipient. Sender does not necessarily endorse content contained within
> > this t
smission.
>
>
>
>
>> Date: Wed, 10 Dec 2008 12:44:45 -0800
>> From: l...@purpleblade.net
>> To: users@maven.apache.org
>> Subject: Re: Is Maven / JUnit 4.x broken (annotations)
>>
>>
>> I looked at my effective pom. I have a dependency there on
w
> would happen. But I'm not sure that was a Maven problem.
>
> Justin
>
>
>
> From: Anders Hammar [mailto:and...@hammar.net]
> Sent: Wed 12/10/2008 6:31 AM
> To: users@maven.apache.org
> Subject: Re: Is Maven / JUnit 4.x brok
Eclipse is a major IDE. Please google!
If you want to use the default surefire plugin configuration you MUST name
your test class according to the default configuration for the surefire
plugin. Please see link provided earlier. If not, you need to configure the
surefire plugin yourself (see link
CheapLisa wrote:
>
> I'm not sure I understand. I don't have the surefire plugin in any of my
> pom's.
Well, if you're not pleased with its default configuration, then it's time
to configure it yourself.
- Jörg
-
To unsubscr
not necessarily endorse content contained within this transmission.
> Date: Wed, 10 Dec 2008 12:44:45 -0800
> From: [EMAIL PROTECTED]
> To: users@maven.apache.org
> Subject: Re: Is Maven / JUnit 4.x broken (annotations)
>
>
> I looked at my effective pom. I have a depe
I can get my tests to execute if the class name ends in Test.java and only if
the method begins
with "testSomeMethod".
otherwise the test will not run. I should be able to name the class
anything I want (not include "Test"), extend TestCase and name the method
anything I want as long as there is
What is the name of your test?
L
Anders Hammar wrote:
>
> Hi,
>
> Just tried it and it works for me, both in Eclipse and from command
> prompt.
> How are you executing?
>
> /Anders
>
>
> CheapLisa wrote:
>>
>> I have JUnit 4.5 as a dependency in my maven pom
>> and I have imported annotat
What's Eclipse?
Also JUnit4 annotations have no restrictions on file nameing if annotations
are used. I simply want
to use the JUnit4 features and not name my files the JUnit 3.x way.
L
Anders Hammar wrote:
>
> Or "*Test.java", or "*TestCase.java". That's the names surefire is
> configured
I looked at my effective pom. I have a dependency there on JUnit 4.5.
The only reference to surefire was maven-surefire-reports-plugin in the
reporting section.
how do I know that surefire is using my dependency of JUnit 4.5? Is maven
bundled with another version of JUnit and using an earlier v
I'm not sure I understand. I don't have the surefire plugin in any of my
pom's. It's in the superpom so I can use it from there.
I have a multi-module project.
L
Jörg Schaible-2 wrote:
>
> CheapLisa wrote at Mittwoch, 10. Dezember 2008 17:16:
>
>>
>> I should not have to name it anything
CheapLisa wrote at Mittwoch, 10. Dezember 2008 17:16:
>
> I should not have to name it anything but put an annotation there like
> @Test. This is OK with JUnit 4.x.
Surefire cannot know which JUnit version you're going to use. So simply
configure the includes of the surefire plugin to use any ja
>> On Wed, Dec 10, 2008 at 12:16 AM, CheapLisa <[EMAIL PROTECTED]> wrote:
>>> I have JUnit 4.5 as a dependency in my maven pom
>>> and I have imported annotations into my test case but
>>> it is not recognizing the @Test and @Ignore annotations.
>>>
>>> I still have to preface the method name with
I should not have to name it anything but put an annotation there like @Test.
This is OK with JUnit 4.x.
Josh Suereth wrote:
>
> I believe the name of the class still matters. Try calling it
> "Test*.java"
>
> On Wed, Dec 10, 2008 at 12:16 AM, CheapLisa <[EMAIL PROTECTED]> wrote:
>
>>
>>
achricht-
Von: Anders Hammar [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 10. Dezember 2008 14:06
An: users@maven.apache.org
Betreff: Re: Is Maven / JUnit 4.x broken (annotations)
Or "*Test.java", or "*TestCase.java". That's the names surefire is configured
for by defau
Or "*Test.java", or "*TestCase.java". That's the names surefire is configured
for by default.
(http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#includes)
I would suggest trying it in Eclipse first. If it works there, then there is
some configuration issue for Maven.
/Anders
I believe the name of the class still matters. Try calling it "Test*.java"
On Wed, Dec 10, 2008 at 12:16 AM, CheapLisa <[EMAIL PROTECTED]> wrote:
>
> I have JUnit 4.5 as a dependency in my maven pom
> and I have imported annotations into my test case but
> it is not recognizing the @Test and @I
ECTED]
Sent: Wed 12/10/2008 6:31 AM
To: users@maven.apache.org
Subject: Re: Is Maven / JUnit 4.x broken (annotations)
Hi,
Just tried it and it works for me, both in Eclipse and from command prompt.
How are you executing?
/Anders
CheapLisa wrote:
>
> I have JUnit 4.5 as a dependency in m
Hi,
Just tried it and it works for me, both in Eclipse and from command prompt.
How are you executing?
/Anders
CheapLisa wrote:
>
> I have JUnit 4.5 as a dependency in my maven pom
> and I have imported annotations into my test case but
> it is not recognizing the @Test and @Ignore annotation
I have JUnit 4.5 as a dependency in my maven pom
and I have imported annotations into my test case but
it is not recognizing the @Test and @Ignore annotations.
I still have to preface the method name with "test"
and the @Ignore tests get executed.
Is something broken? What do I need to do to ge
28 matches
Mail list logo
