Hi, We have seperated some off the different kinds of tests:
- unit test : for the basic tests of our pojo's - integration tests : testing the businesslogic of our components (previously turbine services, now components using a different component container) - sceanrio testing : testing the uses cases of our turbine webapps We only use turbine as MVC controller. We are migrating away from using turbine services and use a different component container (Plexus, but of course you could use any preferred component container) to write components then we can test using unit/integration tests, outside turbine. We use maven 2 as build tool for each of these components and develop them test driven. To test the actual turbine web application (use cases) we started using Selenium. Roger Janssen iBanx -----Original Message----- From: Jeffery Painter [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 24, 2008 3:02 AM To: Turbine Users List Subject: Re: testing question 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] ************************************************************************* The information contained in this communication is confidential and is intended solely for the use of the individual or entity to whom it is addressed.You should not copy, disclose or distribute this communication without the authority of iBanx bv. iBanx bv is neither liable for the proper and complete transmission of the information has been maintained nor that the communication is free of viruses, interceptions or interference. If you are not the intended recipient of this communication please return the communication to the sender and delete and destroy all copies. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
