On second thought of you are unit testing just your jpa classes you shouldn't need the ServletContext to be mocked.
Note that tapestry modules have been split in such a way that Web services are separated from core services. I think your test should not require any web modules. This might require you to split your custom module into 2 modules (web and core) but will make testing easier. On 17 Jul 2014 16:20, "Lance Java" <lance.j...@googlemail.com> wrote: > I'm not sure exactly what you're doing but you probably need to override > the ApplicationGlobals service such that getServletContext() returns an > appropriate mock. > > If you're using junit, you might want to try the new > TapestryIOCJunit4ClassRunner. See the tapestry sources for example test > cases. > On 17 Jul 2014 16:02, "Charlouze" <m...@charlouze.com> wrote: > >> Hello everyone. >> >> I'm currently setting up an application using T5.4-b13. For unit testing, >> I >> use junit, unitils-dbunit, spock (with spock-tapestry and spock-unitils >> extension). >> >> In my specification I added @submodule annotation with every needed module >> (Tapestry, Jpa, beanValidator and my custom module). >> >> My problem is that there are no context and therefore, my tests do not >> pass >> the assert context != null in ContextResource class constructor. Does >> anyone know what can I do ? >> >> Thanks in advance >> >> Charles. >> >
