andrew cooke wrote:
> I wondered about that, but the functional tests module seems to be more
> "support for functional tests" than functional tests itself. That means
> that almost every test depends on mule-tests-functional and again I think
> we get a loop (VM tests depend on mule-tests-functional which would depend
> on VM).
Yup, right about the loop.
> I think they should go in something like a "functional tests" module
> (which is what Andrew suggested too, I think), but the current
What AP suggested is that pretty much exactly what I tried to point out
several times now too, namely that tests that cross compilation units
(artifacts in maven-speak) are actually integration tests which need to go
into their own separate artifacts as well, simply because there is no
other way to avoid the cycles. Each of these integration-test projects
should probably be named after the "tested" dependency, pulling the others
in as needed. So your XML "functional-but-really-integration" test project
could be called e.g. tests/integration-module-xml.
> mule-tests-functional doesn't seem to be it (and should perhaps be renamed
> to mule-module-functional-tests or similar?)
Sounds OK to me since it is essentially the "functional" brother of the TCK
-h
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
