Open GoogleCodeExporter opened 8 years ago
please fix this. This is really annoying
Original comment by belov...@gmail.com
on 12 May 2012 at 9:09
The behavior is a consequence of the design of Spring's TestContext framework.
I don't see a way to change it without hitting other problems. The situation
isn't any different when using the TestContext framework with JUnit.
A @SetupOnce extension that runs before the first feature method of a spec
class might be an effective way to overcome this problem. I'll think about
that. Meanwhile you can write one yourself, or use one of the easier
workarounds outlined in the links provided by the original author of this issue.
Original comment by pnied...@gmail.com
on 12 May 2012 at 9:43
Original issue reported on code.google.com by
stephan....@gmail.com
on 16 Nov 2010 at 11:32