Arnaud,
In my case, I have an interface with several implementations. The
intent is it to have an attached test which verifies that the
implementation conforms to the interface. So each implementation will
include the interface's attached test in addition to it's own unit test.
By including the attached test in each implementation, then anytime an
implementation is successfully built, by Continuum for example, you can
me assured it also confirms to the interface.
Paul Spencer
Arnaud Bailly wrote:
Paul Spencer <[EMAIL PROTECTED]> writes:
Hello,
I think that attached tests are not meant to contain tests that will
be run in another projects but test elements that are useful for reuse
in other (sub)projects. For example, your can have artefactA that have
some tests using some resources and artefactB runnning some tests
using same resources.
Or you have support classes (eg. dedicated Constraint/STub for jmock)
that are reused.
Surefire does not, an in my opinion should not scan a project's test
dependencies for Test classes to run. The maven way (TM) is to create
another project for your (integrations ?) tests if you need as modules
creation and management is cheap.
Hope that helps.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
