I'm curious as to why AppFuse has structured the testing framework it generates in the manner it does; relying on a test applicationContext.xml and extending the Spring test class. We have encountered a great deal of problems with that set up because our actual applicationContext is very different, so our tests can pass, but our application doesn't work as expected.
Are there any reasons for having a dual structure? It seems that the actual applicationContext should be the one that the test framework uses and that extending the Spring Test class only creates another layer of obfuscation and debug problems since you have to learn about setting parameters to control that base test class. Tony -- View this message in context: http://www.nabble.com/General-Comment-Question-about-Functional-Testing-in-AppFuse-tf3310270s2369.html#a9208067 Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
