I (used to) consider myself a somewhat advanced user of Turbine and I have been knocking on this door for some time without good results. Yes, you can setup mock objects and get a long way there, but to employ real functional tests (against a db using the OR model) I have not been successful in setting up a test environment to really test a Turbine based application.
I have a high level of confidence in the Turbine code itself, but if I cannot fully test my applications, then this makes it hard to sell the Turbine platform to others who require tests to show the application will behave as expected. I have been seeking input from other users as well, but have come up short with decent responses. anyone? -- Jeff Painter > > > > > Hello, > > I'm trying to set up testing for a turbine application I have. I'd like to > do this with maven 2 and cactus. > > I've already tried some combinations, but none satisfactory so far. One of > the problems I run into is the database setup. Many test scenarios with > turbine are described without any database integration. I'd like to use > hsqldb. Torque 3.1.1 that comes with turbine 2.3.2 doesn't shut down > correctly the initial definition, so in my tests I cannot startup as in > production, and then change the configuration in the setup of the tests. > What I'm trying now is that in the maven pom the torque.properties gets > overwritten by a testversion when I'm in the test phase. I'm not sure if > this is the right way, though.. > > Also, maven 2 seems only to be integrated with cactus since cactus 1.8.1, > which isn't out yet.. > I was wondering if someone has found a good and proven setup. > > Regards, > Bo > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
