Re: [junitee-user] How to disable JunitEE

[Wade T. <way...@gm...>]

I would recommend creating a new build for the production environment; the
only way you could potentially disable JunitEE is probably through whatever
application server you're using. I also think your concerns about deploying
the application excluding the test classes are extreme. You are putting an
untested "build" in production, but the application has been tested.


-w



On Tue, May 5, 2009 at 6:33 PM, Peter Kelly <pki...@ho...> wrote:

>  I'm new to JunitEE and from reading the documentation it is not clear what
> the approach is to disable the JunitEE TestServlet in production.
>
> JunitEE and associated test classes are being added to an existing
> application so that the test classes can access existing Services and
> infrastructure in the app that is being tested. Once the build is done it is
> installed in the App Server and the JunitEE tests are run. Eventually the
> exact same build will go to production so how do we disable it there or do
> we need to create a new build excluding the JunitEE jars and test classes?
> The preference would be not to create a new build but to somehow disable
> JunitEE. Otherwise we would be testing one app, re-building and essentially
> putting an un-tested build in production.
>
> Any help/suggestions is appreciated.
>
> Regards,
> Peter Kelly
>
>
> ------------------------------------------------------------------------------
> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
> production scanning environment may not be a perfect world - but thanks to
> Kodak, there's a perfect scanner to get the job done! With the NEW KODAK
> i700
> Series Scanner you'll get full speed at 300 dpi even with all image
> processing features enabled. http://p.sf.net/sfu/kodak-com
> _______________________________________________
> junitee-user mailing list
> jun...@li...
> https://lists.sourceforge.net/lists/listinfo/junitee-user
>
>