Even if I use new instances for the requestfactory interface, transport, service layer and etc for each test, it would still share the services between one test and another?
On Fri, Sep 2, 2011 at 11:02 AM, StefanR <[email protected]>wrote: > Caching of services (which are mocks in such a scenario) is a problem > indeed. One easy solution on GWT side would be to have this cache > servlet-specific (i.e. ServiceLayer specific) and not as static field. I > worked around this by calling Mockito#reset() whenever the service > is acquired from my helper class. > > You're right, these are more integration tests than plain junit tests, > however this is absolutely useful, e.g. to test the String parameters in > .with("") methods. The overhead is relatively small. We have some hundred > RF-tests that run within seconds. > > The main problem in my view are the proxy interfaces which are hard to > handle. A POJO based solution (DTOs) would help very much, however, I am not > sure if this is technically possible. > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-web-toolkit/-/Tzv5JS09JTAJ. > > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > -- Magno Machado Paulo http://blog.magnomachado.com.br http://code.google.com/p/emballo/ -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
