On Thu, Jun 5, 2008 at 1:39 AM, Chris Custine <[EMAIL PROTECTED]> wrote:
>> I don't really see why we should not continue using the containers for
>> unit testing. It would be a major work to remove the references to
>> the container, or even to rewrite all the tests using mocks instead of
>> the containers. Furthermore, booting smx3 is very fast and
>> lightweight.
>
>
> I agree with Guillaume here. I definitely want to continue integration
> tests inside the container. I was mainly talking about adding a way to test
> against specific versions of the container or maybe even multiple version in
> the same build? Currently the components inherit the version of the
> container from the parent pom, and we will have to make this a configurable
> property for selecting the container version when running tests.
>
> If anything, a mock strategy could be in addition to the itests, but not
> sure if I would drop integration tests.
I'm not saying we should drop integration testing. You are correct, we
need to find a way to choose to test a given component against the
containers so you can optionally choose to test smx3 or smx4 or at a
unit level.
Bruce
--
perl -e 'print unpack("u30","D0G)[EMAIL
PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache ActiveMQ - http://activemq.org/
Apache Camel - http://activemq.org/camel/
Apache ServiceMix - http://servicemix.org/
Apache Geronimo - http://geronimo.apache.org/
Blog: http://bruceblog.org/
