Re: Test suite naming convention and package hierarchy. Need suggestion....
"Oleskandr" <[email protected]>
| Newsgroups | gmane.comp.java.junit.user |
|---|---|
| Message-ID | <[email protected]> |
David Saff <saff@...> wrote:
>
> I agree that using a simple naming strategy like *Test for individual test
> cases and *Suite for suites is a good solution when sharing tests between
> an IDE and maven.
>
Thanks for answer! Have another related micro-question at bottom of replay...
> If I'm reading right, there's a completely different problem here where
> trying to run DbTests from the command line hangs; I'll have to leave that
> one to others who are more familiar with DbTest, or perhaps the DbTest
> forum itself.
>
I understand and put this test to make better look of my situation...
I don't want to fix this problem as have no time to debug based on project schedule.
And well chosen naming schema workaround this issue (so "mvn test" run only *Test classes and ignore *Suite classes).
> On Mon, Feb 18, 2013 at 10:01 AM, Oleskandr <gavenkoa@...> wrote:
> > To resolve issue I think to rename our test-guites to
> >
> > TestSuite.java
> >
> > to distinct from Test.java pattern. Also I think that it
> > is good practice to move all test-suites to separate package:
> >
> > com/company/project/testsuite/*Suite.java
> >
How about storing all suites in separate single package?
It is easy to locate all available suites without "find . -name '*.Suite.java'"
Is any standard practice on this field?
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/junit/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/junit/join
(Yahoo! ID required)
<*> To change settings via email:
[email protected]
[email protected]
<*> To unsubscribe from this group, send an email to:
[email protected]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/