This was actually my understanding too. We made a
class that builds a test suite dynamically based off
of a directory (starting point) and it now runs all of
our tests in under 2 minutes instead of 30.
Thanks,
Bryan
--- Siegfried Goeschl [EMAIL PROTECTED]
wrote:
Hi Bryan,
I think Maven is
That what you can do:
1. Define a Test Suite with all your tests.
2. Define your pom like that:
unitTest
includes{The TestSuite you created in (1)}/includes
excludes{All tests included at the TestSuite in (1)}/excludes
/unitTest
[]'s
On 6/22/05, bryan hansen [EMAIL PROTECTED] wrote:
This
We are using maven to run our Unit Tests which are
accessing the database through Hibernate. It seems
that when Maven builds the test suite it is
reconfiguring hibernate before each TestCase. So if
there are 3 tests in a class it will run those with
the same configuration, but when it goes to the
Hi Bryan,
I think Maven is not guilty but your approach using static initializer
and singletons is improvable
The JUNIT way
+) of defining a lifecycle for an individual test case is setup() and
tearDown()
+) of providing resources shared across multiple testsuites is using a
TestSetup
it.
..David..
-Original Message-
From: Siegfried Goeschl [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 26, 2005 10:47 AM
To: Maven Users List
Subject: Re: Singletons/static variables and Unit testing
Hi Bryan,
I think Maven is not guilty but your approach using static initializer
