Home/ Questions/Q 146183
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T08:33:24+00:00

In order to run my unit tests on my Eclipse, I need to set

  • 0

In order to run my unit tests on my Eclipse, I need to set some properties for the VM.

Thus, when I first run my JUnit test, I go in ‘Open Run Dialog’, then in my JUnit configuration for this test, I go in ‘Arguments’ tab and put everything I need in the ‘VM arguments’ text area.

Is there a way to automatically add a set of properties when I run my JUnit, so I will be able to only right-click on the test class, and click on ‘Run as > Junit Test’ to run a test?

Technical information: Eclipse 3.3.2, JUnit 4, Java 5

Edit, regarding response from Aaron Digulla:

These properties are used in Spring configuration files*. Thus, I can’t use the idea given by Aaron, as Spring will be initialized before the test is run.

In addition to that, I just need to know if I can achieve that in a easy way in Eclipse. Thus the solution must not have any impact on the compilation of the application outside Eclipse, as my application will finally be compiled (and tested) by Maven2.

* few ‘unit’ tests indeed need my Spring configuration to be run. Ok, I know that it is not real unit tests ;o)

Edit 2: In fact, I was indeed starting the Spring configuration by a test unit. Thus, before starting Spring, I check the System properties, and if my properties are not set, then I give them the required value…

However, I am a little disappointed that Eclipse can’t do that for me automatically…

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. My solution is to create an abstract test base class for all tests in a project which extends TestCase. It has to be abstract so the automatic unit test finder will not consider it.

    In static code block of this class, I set all properties I need. This ensures that the code runs once and only once and that it runs before any test in my project.

    [EDIT] You say that Spring is initialized before the tests run. This is a bug in your project: It must be the tests who initialize Spring. Otherwise, you will always run into the problem that you have to test something outside of your control.

    Therefore, I suggest to move the Spring init code into a place where you can call it at the point in time when the environment is ready.

    Alternatively, check that the environment is correctly set up in setUp() and throw an error if a property is missing. This way, you will at least know why the tests would fail later. But I still prefer to have total control when which subsystem comes to life. Anything else just begs for disaster.

    • 0