> I think it would be quite difficult to automate test writing. I think > Sebastien needs to look differently at the tests. Tests should be > written first and run against an interface w/ mock objects. This is one > of the major benifits of session beans/spring service/ and the whole > DependencyInjection thing. You can model, write a test that matches > your requirements and then implement until your tests pass. > > Now that's not to say that you can't stub the infrastructure out for > testing. You might be able to take it as far as, say, the <<Services>> > and <<Entities>> are now. You draw a line between the service and the > dao and it gives you access to the dao in the service. It doesn't > implement your business logic for you. That would be next to impossible > for any MDA framework today to do.
I didn't want to automate test logic generation but just the structure of tests just to be sure they are complete. Just to be sure everytime some implementation class is generated (waiting for replacing todo's by actual implementations), a test class is generated to with convenient method, as well as any configuration files needed to make testing environment ready to run. WDYT ? -- Sebastien ARBOGAST ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r _______________________________________________ Andromda-user mailing list Andromda-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/andromda-user
