Re: Test suite naming convention and package hierarchy. Need suggestion....
David Saff <[email protected]>
| Newsgroups | gmane.comp.java.junit.user |
|---|---|
| Message-ID | <CALrw-Py+i8hcOxm6RverNM7Zc0iOGsVrh40k=dfYPX1hGV7G7Q@mail.gmail.com> |
Oleskandr, 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. 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. Good luck, David On Mon, Feb 18, 2013 at 10:01 AM, Oleskandr <[email protected]> wrote: > ** > > > I ask my question at: > > > http://stackoverflow.com/questions/14894067/path-or-naming-shema-for-files-with-classes-that-marked-by-suiteclasses-junit4 > > and don't receive any answer. So I read JUnit FAQ and post here... > > I involved into project where: > > * Test files with classes which marked as @SuiteClasses placed > in same packages as regular tests. > > This cause problem that test eexecuted twice or more times on "mvn test": > > includes tags for surefire plug-in look like > com/company/project/core/**/*Test.java in our pom.xml > > we have naming schema for suites like: SuiteTest.java > > * Recently I integrate DbUnit to project. Running DbUnit test > from IDE or test-suite which refer for DbUnit tests from IDE > are ok. > > But from command line it stuck on DbUnit test forever if any > test-suite refer to any DbUnit tests. > > This cause CI Jenkins to stop building and delivering project > build to manual-test team... > > ================================================================ > > 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 > > Some points to naming schema I fount in FAQ: > > http://junit.sourceforge.net/doc/faq/faq.htm#organize > > but FAQ is silent about test-suites... > > Any suggection for best practice for naming suites are welcome! > > > [Non-text portions of this message have been removed] ------------------------------------ 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/