Kathey Marsden wrote:
Upon more research it seems that JUnit creates one instance of each
test class per fixture and keeps that reference until the end of the
suites.All run. That means any state in the test hangs around as
well, which slowly adds up as the test runs. This is particularly
pro
Upon more research it seems that JUnit creates one instance of each test
class per fixture and keeps that reference until the end of the
suites.All run. That means any state in the test hangs around as well,
which slowly adds up as the test runs. This is particularly problematic
for tests such
