Hi,
Currently WSIF unit tests are loosely themed and test function in multiple
providers. For instance jms.JmsTest tests <jms:address, <jms:property and
<jms:propertyValue tags across the SoapJms, AxisJms and NativeJms
providers. You can either run a specific unit test or run all of them by
running util.WSIFTestRunner. wsif.test.properties has
wsif.test.components=ejb=on,jms=on,remotewsdl=on,jndi=on,fix=on,async=on
which allows you to switch off areas across all unit tests. So because I
rarely change the EJB provider, I run with ejb=off so when I run
WSIFTestRunner none of the EJB tests get run. This can be dangerous and it
is generally better to run all the unit tests. Individual unit tests can
call TestUtilities.areWeTesting("ejb") for instance. There are various
listeners needed to run the unit tests (JMS2HTTPBridge, JMSAsyncListener,
NativeJMSRequestListener) and unit tests automatically start and stop the
listeners that they need.
I agree with Nirmal and Alek. As I have added in unit tests I have focussed
more on test coverage than on modularity, documentation and ease-of-use. I
think I am happy with the idea that tests and groups of tests have themes,
whereas wsif.test.components can switch components. But the themes and
components could be better organised. There should be a component for every
provider at least. As the number of unit tests grows (227 currently), it
takes longer to run them all. So maybe there could be a
wsif.test.howmuch=few | most | all which would run a different subset of
the tests.
What do you think?
Mark
Mark Whitlock, IBM Hursley, Web Services
----- Forwarded by Mark Whitlock/UK/IBM on 18/10/02 09:51 -----
Aleksander
Slominski To: [EMAIL PROTECTED]
<[EMAIL PROTECTED] cc:
.edu> Subject: Re: [WSIF] Organizing unit
tests
18/10/02 06:32
Please respond to
axis-dev
Nirmal Mukhi wrote:
> I can certainly help since I'm a perfect guinea pig, my runtime
environment
> is very basic - I just use a JRE with Tomcat as my web server. I don't
have
> any JMS product and would have to install a free one to test the JMS
> provider and SOAP/JMS support. So if somebody (Mark? ;-)) volunteers to
> reorganize the tests and start the documentation, I can help verify it is
> sufficient, and also assist in the documentation based on my testing
> experience.
hi,
i can only second this :-) my runtime environment is mostly w2k and linux
and i volunteer to do testing as well (and to work on resolving issues
and to write down all that is necessary to get tests running ...)
i think the most important is to get to get required JMS setup to work
and to make tests/setup JMS implementation independent as much as possible
and then to document it well. by default tests could use an open source
JMS impl
such as OpenJMS (http://openjms.sourceforge.net/) or Open3.org
(mentioned in http://www.onjava.com/pub/a/onjava/2002/06/19/jms.html
but Open3.org site seems be down right now and i am not sure if it is
still available ...).
using open source JMS implementation would allow us to embed required JAR
files
and make running tests less painful - we would still need to write
additional documentation
on how to set tests for all other kinds of JMS impls and maybe simplify it
by
providing some kind of configuration files for different JMS impls?
thanks,
alek
