*bump* this one because I think a question still remains unanswered. There is a need for have a) unit tests run against database settings 1 (populated by dbUnit) and b) the real application deployment war run against a different database settings 2
The whole point of dbUnit is to run against a different database, dedicated to unit testing. However I can't figure out how to do a mvn install, so that unit tests are run against a different db than the final war. There must be a way to do this? Joachim Ansorg-3 wrote: > > Hi Rob, > thanks for the second reply. >>> Did you solve that problem somehow or do you just skip the tests in >>> env-dev? >>> >> >> That's evidently by design. For tests to work reliably they have to have >> the >> DB in a known state. >> >> > I assumed that, too. So I've tried to configure appfuse to use a > different database for the tests, i.e. src/main should use db1 and > src/test/ should use db2. So that the main app and the tests are > independent from each other. > But since I failed I will follow your approach. > And profiles are a good idea, anyway. > > Thanks again, > Joachim > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/cargo-maven2-plugin%3A-Configuration-for-seperate-test-database--tf4677233s2369.html#a13425371 Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
