Hello,
As some of us have discussed, WSIF unit tests are extremely useful but
complex to run because of the environment required. The major reason for
the complexity is the number of providers we have and the setup required
for each. One of our long term goals is to modularise WSIF (so a particular
WSIF installation may include any providers that were required, not have to
have all of them). Modularising testing too is a big part of this. So if I
elect to have only java and EJB providers (for example) in my WSIF
installation, the test runner would run only those tests.
Doing this will take some effort. But documenting the testing procedure is
a good start. It would be great especially if we could organize the test
cases into "core" test cases (that exercise the core WSIF API) and test
cases for each provider. Then we can document how to set up an environment
for each set of provider test cases, and write scripts that help you run
them.
Do you agree with this direction?
If so we need to reorganize the test cases first (I'm thinking a clearer
directory structure and a couple of clever scripts should be all that is
required), and write the documentation (which should give step by step
instructions on how to run each set of test cases, and hints to developers
on how to write a test case and add it to an existing set). Volunteers?
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.
Nirmal.
