RE: Regarding Unit Tests

All openjms tests are located under src/testharness,
and are invoked by the test.bat/.sh scripts. 
In the short term, its probably easiest to put any
unit tests under this structure. When maven 1.0 b8 is
released (http://jakarta.apache.org/turbine/maven/) 
I will be restructuring the tests to separate them on a
unit/integration basis.

The iiop code is commented out in the build.xml. I don't
know if JBuilder can exclude files from compilation - if not,
just remove them locally.

Regards,

Tim
  

> From: openjms-developer-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> [mailto:openjms-developer-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org]On Behalf Of Day,
> Jem BGI WAC
> Sent: Wednesday, February 05, 2003 10:58 AM
> To: [ML] openJMS - Dev (E-mail)
> Subject: [openjms-developer] Regarding Unit Tests
> 
> Hi,
> 
>   Can somebody outline the unit test strategy, if i'm reading everything
> correctly it looks
>   like the current tests are more 'functional' in nature as 
> opposed to basic
> class testing.
> 
>   I can across this as i was intending to modify a class but 
> thought it'd be
> a good idea
>   to have a test case so that i could ensure i hadn't broken 
> anything at the
> class level. I
>   then realized that the main build.xml file doesn't appear to 
> run any unit
> tests.
> 
>   Can somebody enlighten me please.
> 
>   Also, Is anybody using JBuilder to work on this code base, if so could
> they send
>   me a .jpx file - i don't seem to be able to get the iiop stuff to
> compile..
> 
> Thanks
> 
> jem..
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
> http://www.vasoftware.com
> _______________________________________________
> openjms-developer mailing list
> openjms-developer-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/openjms-developer
>