When I test my component and service classes, that is UNIT test them, I use mocks; since I'm generally using Groovy and Spock, it is easy to inject even into a private field.
Later, I do integration testing, where I bring up the application as closely as possible to how it works in production (but targeting a different database, etc.). That not only acts like a sanity check, and a chance to test the behavior in the browser, but also tests all the wiring of services inside modules, and injections into pages and components ... that is, the interactions between the lowest level structures. Tapestry's PageTester provides an interrum level, running the application inside a simulated servlet container. On Tue, Nov 6, 2012 at 8:32 AM, Thiago H de Paula Figueiredo < thiag...@gmail.com> wrote: > On Tue, 06 Nov 2012 14:00:41 -0200, Taha Siddiqi <tawus.tapes...@gmail.com> > wrote: > > Try adding TapetryModule.class, TapestryIOCModule.class to the >> registryBuilder using registryBuilder.add(..). (Although I think >> IOCUtilities.**addDefaultModules() does that.) >> > > I forgot to mention that TapestryFilter is the one who does that. > > > -- > Thiago H. de Paula Figueiredo > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > users-unsubscribe@tapestry.**apache.org<users-unsubscr...@tapestry.apache.org> > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com
