The important task here is getting the tests right.
Getting the tests right and also making sure that they are automated and require very little effort to run. If it's not a big deal to run the tests, then perhaps developers can incorporate testing into their development process. By that I mean running the tests before the commit happens. It's a change in attitude and habit but it may be worth the effort.
Building on SVN commit would be nice but probably complicated to set up.
It might even be impossible to set up because the SVN server may not have the proper development environment for running tests. It is ideal to have an automated system in place to ensure failing tests are caught before code gets committed, but "mvn test" (and a change in mindset) should be all that's required to run tests manually. Sorry if I seem to be preaching XP practices but that's what I believe. Cynick --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SAIL-Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/SAIL-Dev?hl=en -~----------~----~----~----~------~----~------~--~---
