junit4

When using this approach below, by setting up the jUnit with Suites. We got the problem when all @BeforeClass in every Testclass will be executed before any tests starts to execute. (For each n TestClass file the @BeforeClass runs, then after they have execute, it started to execute the first MyTest.class files @Test) This will cause that we allocate up much resources and memory. My thoughts was that it must be wrong, shouldn't each @BeforeClass run only before the actual testclass is executed, not when the Suite is started? @RunWith(Suite.class) @Suite.SuiteClasses({ MyTests.class, Mytests2

I know this is bad practice, but it needs to be done, or I'll need to switch to testng . Is there a way, similar to JUnit 3's testSuite, to specify the order of the tests to be run in a class? Michael D If you're sure you really want to do this: There may be a better way, but this is all I could come up with... JUnit4 has an annotation: @RunWith which lets you override the default Runner for your tests. In your case you would want to create a special subclass of BlockJunit4ClassRunner , and override computeTestMethods() to return tests in the order you want them executed. For example, let's

I believe that we are all know that setUp (@Before) will execute before any test method and tearDown(@After) will execute after test method. Also we know that Junit will create one instance of Test per test method . my question is that can we just move setUp method content to class Constructor and remove setUp method? is there any specific reason to keep setUp method? This (old) JUnit best practices article puts it like this: Do not use the test-case constructor to set up a test case Setting up a test case in the constructor is not a good idea. Consider: public class SomeTest extends TestCase

In my project I have to do some repository setup before all tests. This is done using some tricky static rules. However I've got no clue how to do clean up after all the tests. I don't want to keep some magic static number referring the number of all test methods, which I should maintain all the time. The most appreciated way is to add some listener which would be invoked after all the tests. Is there any interface for it already in JUnit4? edit: this has nothing to do with @BeforeClass and @AfterClass, cause I have to know if method annotated with @AfterClass is invoked for the last time.

When I run my unit tests, it invokes my scheduled tasks. I want to prevent this behaviour, which is caused by the fact that I have @EnableScheduling on my main app configuration. How can I disable this on my unit tests? I have come across this question/answer which suggests setting up profiles? Not sure how I would go about that? or if its an overkill? I was thinking of having a separate AppConfiguration for my unit tests but it feels like im repeating code twice when I do that? @Configuration @EnableJpaRepositories(AppConfiguration.DAO_PACKAGE) @EnableTransactionManagement @EnableScheduling

I'm using JUnit Categories and ClassPathSuite in a setup similar to that described in this answer . To recap: public interface FastTests { } @RunWith(Categories.class) @Categories.IncludeCategory(FastTests.class) @Suite.SuiteClasses(AllTests.class) public class FastTestSuite { } @RunWith(ClasspathSuite.class) public class AllTests { } ...where AllTests makes use of the ClasspathSuite library. A test class that's part of the FastTests category would look like this: @Category(FastTests.class) public class StringUtilsTest { // ... } When I run "FastTestSuite" in my IDE, all tests with the