Hi! This has been discussed previously. But I would like to ask the list again, how do you separate integrations test from unit tests in a Maven project?
I define unit tests as being tests that will run in memory and not use any external resources. Anything external is mocked away. Everything will run in memory and as fast as possible. I define integration tests as tests that are dependent on other resources than the source code. This is (at least): * The file system * Databases * Network access Assume that we are dealing with a multi module build, how would you organize the modules? Would you consider adding a separate 'integration-test' tree next to main and test? /Thomas -- Thomas Sundberg M. Sc. in Computer Science Mobile: +46 70 767 33 15 Blog: http://thomassundberg.wordpress.com/ Twitter: @thomassundberg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
