We'll have to talk about mocking over the weekend, probably going to need a lesson in it ;) Unit testing is still pretty new to me, so lots to learn yet.
On Wed, Sep 10, 2014 at 12:40 PM, Lance Java <lance.j...@googlemail.com> wrote: > Testing web stuff gets a bit messier, as I said before I usually have > simple pass throughs from web to api and concentrate my unit testing on the > api layer. > > Having two modules can really define this separation and forces you to do > the right thing. > > Loading all the tapestry web module gets messy since you'll need to mock > the ServletContext and various other bits. It's usually easier to fire up a > test webapp in jetty. > On 10 Sep 2014 17:29, "Lance Java" <lance.j...@googlemail.com> wrote: > > > Hi George, PageRenderLinkSource is a part of the web framework. > > > > I mentioned before that you could split your app into 2 modules: > > api - depends on tapestry-ioc > > web - depends on tapestry-core > > > > The test case I setup for you only tests the api stuff (tapestry-ioc). If > > you split into 2 modules this would be easy to see (since > > PageRenderLinkSource would not be on the test classpath). > > > -- George Christman www.CarDaddy.com P.O. Box 735 Johnstown, New York
