On Thu, Jun 5, 2008 at 1:53 AM, Gert Vanthienen
<[EMAIL PROTECTED]> wrote:
> L.S.,
>
> I agree it would be good thing to make a distinction between unit tests and
> integration tests. We should probably have both of them: unit tests could
> use the mock test framework and for the integration tests, we should keep on
> using the containers.
>
> For the integration tests, wouldn't it be possible to write most of them in
> a form that allows to test them on both versions of the container
> automatically. Another idea (probably slightly out-of-scope for now)= we
> could look into is doing multiple integration tests with a single container
> instance. The Maven itests should allow us to:
> - start a container in pre-integration-test
> - deploy/test/undeploy for a set of integration tests
> - stop the container in post-integration-test
>
> This should reduce the overhead of starting/stopping the container over and
> over again, making the tests easier/faster to run -- I know the container is
> lightweight thing, but it should still make a difference, no?
Well I guess the one thing that we'd need to address would be
resetting the state of the container before each test is run. Right
now we have no easy way to achieve this, but we could create a
convenience method for it I suppose.
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/
