I would tend to use a mock IComponentSpecification, or a hand initialized one.
There are not any magic tools here, though I suspect a lot of the plumbing could be moved into base classes or helper classes. On 6/4/07, carlos f <[EMAIL PROTECTED]> wrote:
Howard Lewis Ship wrote: > > But an integration test (either relatively contained, such as creating the > EnhancementOperationImpl, or wider, such as firing up the app and testing > with selenimum) is the only worthwhile way to > ensure that generated code is correct. > I would like to as tightly constrain this as possible, newing up an EnhancementOperationImpl and other associated classes to test my enhancement. The generatation of a IComponentSpecifiction instance seems to touch a number of classes. Do you have any advice on how best to do this? Should I try to spin up hivemind for the test or just new up the object graph that is required in this interaction? Is there any testing utility that I may be missing? Carlos -- View this message in context: http://www.nabble.com/Unit-Testing-EnhancementWorkers-tf3867100.html#a10956427 Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com
