On 11/12/07, mfs <[EMAIL PROTECTED]> wrote: > > Can "java/src/test" be used to package both unit and integration tests > ? Or > this structure specifically for the unit test-cases.. ?
Yes, it can be used for both. Typically you'd name your pure unit tests as something like *UnitTest.Java and integration tests as *IntegrationTest.java, then bind surefire-plugin another time to a different phase and supply a different configuration (say start a container first) for running the integration tests. Like for example in my case we have an html file used for some > functional/integration testing, would it be a good idea to put it in the > java/src/test folder ? > > It depends on what your integration tests are like. If they are fairly simple and meant to be run pretty much all the time, I'd just put them in. If they are more comprehensive, need specific configuration/environment and/or are run only conditionally because they for example take a long time to run, you may want to consider separating into their own "test" module - the advantage is that it can have it's (release) lifecycle, run separately etc, as in a form of TCK (Test Compatibility Kit). Kalle
