Also note that JUnit explicitly does not support this. TestNG *can* but
you have to explicitly tell it about the dependency from one test to the
next.
On Mon, 2009-08-24 at 09:16 -0500, Steve Ebersole wrote:
> If tests rely on the state from previous tests, that's a bad setup. The
> issue we hav
If tests rely on the state from previous tests, that's a bad setup. The
issue we have seen is that the tests can be run in different orders
based on the jvm used.
On Mon, 2009-08-24 at 13:18 +0200, Emmanuel Bernard wrote:
> Any hint on why this is failing? The most sensitive tests are the
> perf
Any hint on why this is failing? The most sensitive tests are the perf
tests and the JMS ones. The others should be fixable wo too much effort.
On 24 août 09, at 10:35, Hardy Ferentschik wrote:
> On Sun, 23 Aug 2009 12:33:05 +0200, Emmanuel Bernard > wrote:
>
>> Hibernate Search test suite use
On Sun, 23 Aug 2009 12:33:05 +0200, Emmanuel Bernard
wrote:
> Hibernate Search test suite used to run in about 2 mins. Now it runs
> in a solid 7 minutes. Can we get that number back?
The problem is that in forkMode=once some of the tests are failing -
LazyCollectionsUpdatingTest
and Embedde
Hibernate Search test suite used to run in about 2 mins. Now it runs
in a solid 7 minutes. Can we get that number back?
It seems like maven is pausing between tests or something like that.
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
ht
