Re: [Stripes-dev] Test components

[Joshua Chaitin-P. <jo...@as...>]

I checked the mock package, and most of the classes have any Stripes
imports, so they could be setup the way you suggest, but it looks like
MockRoundtrip has dependencies on core Stripes classes, so that might be a
bit tricky to refactor.

MockRoundtrip imports the following classes:

import net.sourceforge.stripes.action.ActionBean;
import net.sourceforge.stripes.controller.ActionResolver;
import net.sourceforge.stripes.controller.AnnotatedClassActionResolver;
import net.sourceforge.stripes.controller.StripesConstants;
import net.sourceforge.stripes.controller.StripesFilter;
import net.sourceforge.stripes.controller.UrlBindingFactory;
import net.sourceforge.stripes.util.CryptoUtil;
import net.sourceforge.stripes.validation.ValidationErrors;


On Sun, Apr 6, 2014 at 2:00 PM, Larry Meadors <lar...@gm...>wrote:

> I wouldn't suggest that, either.
>
> The mocks are used in the stripes project tests, which makes sense -
> they are super useful (I use them in my projects, too).
>
> I think ideally, the structure would look like this:
>
> - stripes-test (mocks)
> - stripes (main code and tests; dependency on stripes-test)
> - examples (main code and tests; dependency on stripes & stripes-test)
>
> Larry
>



-- 
Joshua Chaitin-Pollak
Chief Technology Officer
Assured Labor, Inc.
www.assuredlabor.com
www.empleolisto.com.mx
www.trabalhoja.com.br