blocks|key|350858|text|我的解决方案是为扩展TestCase的项目中的所有测试创建一个抽象测试基类。它必须是抽象的，所以自动单元测试查找器不会考虑它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|350859|在这个类的静态代码块中，我设置了我需要的所有属性。这确保代码只运行一次，并且在我的项目中的任何测试之前运行。|350860|编辑您说Spring是在测试运行之前初始化的。这是你项目中的一个bug+:一定是测试初始化了Spring。否则，您总是会遇到这样的问题，即您必须测试一些您无法控制的东西。|350861|因此，我建议将Spring+init代码移到一个您可以在环境准备好的时候调用它的地方。|350862|或者，检查是否在setUp()中正确设置了环境，如果缺少属性，则抛出错误。这样，您至少可以知道为什么测试以后会失败。但当哪个子系统启动时，我仍然更喜欢完全控制。其他任何事情都只会招致灾难。|350863|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

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.

blocks|key|345946|text|当我想要为我的junit测试设置一些属性条目时，我实现了以下内容|type|unstyled|depth|inlineStyleRanges|entityRanges|data|345947|protected+void+setUp()+throws+Exception+{
++++++++super.setUp();

++++++++System.setProperty("Property1",+"value1");
++++++++System.setProperty("Property2",+"value2");
}|code-block|syntax|javascript|345948|属性是在调用测试方法之前设置的|345949|编辑:您还可以从文件中读取属性，并从文件中读取系统属性|345950|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

When i want to set some properties entries for my junit test i implement the following

<pre><code>protected void setUp() throws Exception {
 super.setUp();

 System.setProperty("Property1", "value1");
 System.setProperty("Property2", "value2");
}
</code></pre>

The properties are set before the test methode is called

EDIT:
You also can read the properties from a file and at thes to the System properties

blocks|key|348256|text|我从来不明白为什么启动配置可以定义环境变量，但是添加系统属性的唯一方法似乎是添加vm参数。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|348257|我解决这个问题的方法是让测试(或抽象测试基类)测试所需属性的存在，如果它们不存在，则从类路径上的.properties文件加载它们。|348258|这是因为我仍然可以覆盖它们，或者从ANT或Maven中指定它们，但也可以‘右键单击’->+Run+as+->+Junit+Test各个测试文件。|348259|编辑:下面是一个示例，让Spring以与上述相同的方式有选择地加载属性文件：|348260|<bean+id="placeholderConfig"+class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
++++++++<property+name="location"+value="database.properties"/>
++++++++<property+name="ignoreResourceNotFound"+value="true"+/>
++++++++<property+name="systemPropertiesMode">
++++++++++++<util:constant+static-field="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer.SYSTEM_PROPERTIES_MODE_OVERRIDE"+/>
++++++++</property>
</bean>|code-block|syntax|javascript|348261|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Q|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|R|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|S|8|@]|9|@]|A|$K|L]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

I never understood why the launch configurations have a way to define environment variables but the only way of adding a system property seems to be to add vm arguments.

The way I've worked around this is to have tests (or an abstract tests base class) test for the presence of required properties, if they aren't there then I load them from a .properties file on the classpath.

This works as I can still override them or specify them from ANT or Maven but can also 'right click' -> Run As -> Junit Test the individual test files.

edit: here is an example of getting Spring to optionally load a properties file in the same manner as described above:

<pre><code>&lt;bean id="placeholderConfig" class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"&gt;
 &lt;property name="location" value="database.properties"/&gt;
 &lt;property name="ignoreResourceNotFound" value="true" /&gt;
 &lt;property name="systemPropertiesMode"&gt;
 &lt;util:constant static-field="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer.SYSTEM_PROPERTIES_MODE_OVERRIDE" /&gt;
 &lt;/property&gt;
&lt;/bean&gt;
</code></pre>

blocks|key|350895|text|你可以试试这个--转到|type|unstyled|depth|inlineStyleRanges|entityRanges|data|350896|+Window->Preferences->Java->Installed+JREs|code-block|syntax|javascript|350897|ans选择正在使用的JVM，然后放入一个“默认VM”参数，如|350898|++-DrunningInEclipse|350899|然后你可以从你的TestCase中进行检查：|350900|+++System.getProperty("runningInEclipse")+!=+null|350901|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

You could try this - go to 

<pre><code> Window-&gt;Preferences-&gt;Java-&gt;Installed JREs
</code></pre>

ans select the JVM in use, than put a "Default VM" prameter like 

<pre><code> -DrunningInEclipse
</code></pre>

Than you can check from within your TestCase:

<pre><code> System.getProperty("runningInEclipse") != null
</code></pre>

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

<hr>
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...

Automatically add properties when running JUnit in Eclipse

单元测试

Eclipse

Java

为了在Eclipse上运行单元测试，我需要为VM设置一些属性。因此，当我第一次运行JUnit测试时，我进入"Open run Dialog"，然后在这个测试的JUnit配置中，我进入"Arguments“选项卡，并将所需的所有内容放在"VM arguments”文本区域中。有没有一种方法可以在我运行JUnit时自动添加...

问在Eclipse中运行JUnit时自动添加属性
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在Eclipse中运行JUnit时自动添加属性EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在Eclipse中运行JUnit时自动添加属性
EN