Though, I think that we will find that once the Examples application is available, it will turn into a fertile ground for testing the integration of new features. Rather than trying to stretch the MailReader to fill a new use case, we can do a use-case example and make that another of the Examples.
I'm working on a cookbook project that does this for a ton of examples. It takes a bit of work to keep it all together, but with a few simple conventions, it can be quite manageable.
For taglibs, I'd suggest we try to add or extend a taglib-exercise for any new tag or tag enhancement, but IMHO those tests work best as simple Model 1 creatures without dependencies on other objects.
-Ted
David Graham wrote:
However we combine the apps I want to make sure MailReader continues to be suitable for testing changes in. I often run through and/or modify MailReader to test changes before committing them.
David
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
