blocks|key|1261571|text|如果你因为进行单元测试而采取不同的方式，那么你就违背了单元测试的目的。单元测试应该像生产环境一样执行(除了设置和删除任何必要的数据，以及包含在JUnit测试本身而不是您的代码中的need....but+)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1261572|但是，如果您确实有充分的理由这样做，我会查看堆栈，看看JUnit是否在那里。|1261573|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

If you're doing things differently because you're doing a unit test you're defeating the purpose of a unit test. A unit test is supposed to perform exactly like production would (except for the setup and teardown of any necessary data and such you need....but that is included in the JUnit test itself and not your code).

However, if you truly do have a good reason for this I'd look at the stack and see if JUnit is there.

blocks|key|1261631|text|首先，这可能不是一个好主意。您应该单元测试实际的生产代码，而不是稍微不同的代码。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1261632|如果您真的想这样做，您可以查看堆栈跟踪，但由于您无论如何都要为此更改程序，所以您不妨在代码中引入一个新的静态布尔值字段isUnitTesting，并让JUnit将其设置为true。保持简单。|offset|length|style|CODE|1261633|entityMap^0|0|1N|D|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

First of all, this a probably not a good idea. You should be unit testing the actual production code, not slightly different code. 

If you really want to do this, you could look at the stacktrace, but since you are changing your program for this anyway, you might just as well introduce a new static boolean field <code>isUnitTesting</code> in your code, and have JUnit set this to true. Keep it simple.

blocks|key|1261661|text|如果你想以编程方式决定运行哪个“配置文件”，这可能是一个好主意。考虑一下用于配置的Spring+Profiles。在集成测试中，您可能希望针对不同的数据库进行测试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1261662|下面是测试过的代码，可以正常工作|1261663|public+static+boolean+isJUnitTest()+{++
++for+(StackTraceElement+element+:+Thread.currentThread().getStackTrace())+{
++++if+(element.getClassName().startsWith("org.junit."))+{
++++++return+true;
++++}+++++++++++
++}
++return+false;
}|code-block|syntax|javascript|1261664|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

It might be a good idea if you want to programmatically decide which &quot;profile&quot; to run. Think of Spring Profiles for configuration. Inside an integration tests you might want to test against a different database.
Here is the tested code that works
<pre><code>public static boolean isJUnitTest() { 
 for (StackTraceElement element : Thread.currentThread().getStackTrace()) {
 if (element.getClassName().startsWith(&quot;org.junit.&quot;)) {
 return true;
 } 
 }
 return false;
}


 
</code></pre>

blocks|key|1261751|text|这个帖子上的许多人说，在JUnit下运行稍微不同的代码不是一个好主意。我大体上同意，但我认为也有一些例外。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1261752|例如，我目前正在为连接到数据库的应用程序编写集成(而不是单元)测试。|1261753|这些验收测试通常需要使用特定的测试数据完全重新初始化DB。|1261754|显然，我永远不希望在实际的生产数据库上执行此操作，因为这可能会完全擦除有价值的生产数据。|1261755|保证这种情况永远不会发生的最简单方法是，当代码在JUnit下运行时，使其不能连接到生产数据库。例如，如果生成连接的工厂可以知道它是在JUnit下运行的，并且在这种情况下，将返回空连接，则可以反过来执行此操作，除非我们尝试连接的数据库具有已知为测试数据库的名称(例如："testdatabase")。|1261756|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|$]]

Lots of people on this thread say that it's a bad idea for code to run slightly differently while under JUnit. I generally agree, but I think there are some exceptions.

For example, I am currently writing INTEGRATION (as opposed to Unit) tests for an app that connects to a DB.

These acceptance tests often need to completely reinitialize the DB with specific test data.

Obviously, I don't want this EVER, EVER to be done on an actual production DB, because that might completely erase valuable production data.

The easiest way to guarantee that this will never happen, is to make it impossible for the code to connect to a production DB when it is running under JUnit. This in turn can be done if, for example, the Factory that generates a connection can tell that it's running under JUnit, and in that case, will return a null connection unless the database we are trying to connect to has a name that is known to be a test database (ex: "testdatabase").

blocks|key|895387|text|当使用Spring时，可以定义一个包含这个值的bean。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|895388|在应用程序上下文中：|895389|@Bean
public+boolean+isRunningTests()+{
++++return+false;
}|code-block|syntax|javascript|895390|在测试应用程序上下文中：|895391|@Bean
public+boolean+isRunningTests()+{
++++return+true;
}|895392|将值注入Spring组件：|895393|@Resource
private+boolean+isRunningTests;

private+void+someMethod()+{
++++if+(isRunningTests())+{
++++++++....|895394|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|V|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|W|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|P|5|F|7|Y|8|@]|9|@]|A|$G|H]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

When using Spring one can define a bean which holds this value.

In application context:

<pre><code>@Bean
public boolean isRunningTests() {
 return false;
}
</code></pre>

In test application context:

<pre><code>@Bean
public boolean isRunningTests() {
 return true;
}
</code></pre>

Inject the value to a Spring component:

<pre><code>@Resource
private boolean isRunningTests;

private void someMethod() {
 if (isRunningTests()) {
 ....
</code></pre>

blocks|key|898058|text|这与用户的问题没有严格的关系，但我非常确定，达到这个目的的人可能会发现它很有用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|898059|我使用以下方法:公开将在测试中使用的包本地构造函数。|898060|例如：|898061|898062|源/main/java/ApplicationService.java|blockquote|898063|898064|898065|public+class+ApplicationService+{
++private+final+Integer+someInternalObject;

++public+ApplicationService(String+somePublicArgument)+throws+NumberFormatException+{
++++someInternalObject+=+Integer.valueOf(somePublicArgument,+16);
++}

++ApplicationService(Integer+someInternalObject)+{
+++++this.someInternalObject+=+someInternalObject;
++}
}|code-block|syntax|javascript|898066|898067|源/测试/应用服务测试.Java|898068|898069|898070|public+class+ApplicationServiceTest+{
++@Test
++public+void+testSomething()+throws+Exception+{
++++ApplicationService+applicationService+=+new+ApplicationService(0);
++}
}|898071|将其公开给所有测试|898072|不是期末课程|898073|在测试中扩展它，并为包提供一个公共构造函数-本地的或受保护的。|898074|最终类|898075|在将使用包本地构造函数创建它的同一个包中(在测试中)创建一个公共Factory+Method。|offset|length|898076|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/Factory_method_pattern^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|W|E|0|0^^$0|@$1|2|3|4|5|6|7|1H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]|$1|G|3|H|5|I|7|1L|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|1M|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|1N|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|1O|8|@]|9|@]|A|$O|P]]|$1|Q|3|-4|5|6|7|1P|8|@]|9|@]|A|$]]|$1|R|3|S|5|I|7|1Q|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1R|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1S|8|@]|9|@]|A|$]]|$1|V|3|W|5|N|7|1T|8|@]|9|@]|A|$O|P]]|$1|X|3|Y|5|6|7|1U|8|@]|9|@]|A|$]]|$1|Z|3|10|5|6|7|1V|8|@]|9|@]|A|$]]|$1|11|3|12|5|6|7|1W|8|@]|9|@]|A|$]]|$1|13|3|14|5|6|7|1X|8|@]|9|@]|A|$]]|$1|15|3|16|5|6|7|1Y|8|@]|9|@$17|1Z|18|20|1|21]]|A|$]]|$1|19|3|-4|5|6|7|22|8|@]|9|@]|A|$]]]|1A|$1B|$5|1C|1D|1E|A|$1F|1G]]]]

this is not strictly related to the user question, but I'm pretty sure that someone that get there may find it useful.

I use the following approach: expose a package-local constructor that will be used from tests.

e.g.

<blockquote>
 src/main/java/ApplicationService.java
</blockquote>

<pre><code>public class ApplicationService {
 private final Integer someInternalObject;

 public ApplicationService(String somePublicArgument) throws NumberFormatException {
 someInternalObject = Integer.valueOf(somePublicArgument, 16);
 }

 ApplicationService(Integer someInternalObject) {
 this.someInternalObject = someInternalObject;
 }
}
</code></pre>

<blockquote>
 src/test/ApplicationServiceTest.Java
</blockquote>

<pre><code>public class ApplicationServiceTest {
 @Test
 public void testSomething() throws Exception {
 ApplicationService applicationService = new ApplicationService(0);
 }
}
</code></pre>

<h2>expose it to all tests</h2>

<h3>not final classes</h3>

Extend it in the tests and provide a public constructor for the package-local or protected one.

<h3>final classes</h3>

Make a public <a href="https://en.wikipedia.org/wiki/Factory_method_pattern" rel="nofollow">Factory Method</a> in the same package ( within tests ) that will create it using the package-local constructor.

blocks|key|149324|text|如何检查junit+jar是否在类路径中？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|149325|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

How about checking if the junit jar is in the classpath?

blocks|key|1261941|text|为了区分test和no+test，您总是可以在application-test.properties中定义特殊的属性或值。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1261942|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In order to distinguish between test and no test you can always define special property or value in application-test.properties.

blocks|key|149885|text|最短(代码最少)的解决方案是设置一个全局标志，该标志在测试正在而不是运行时设置。然后，您可以在main()+(或类似的入口点)中设置它一次，而不是在所有测试类的设置方法中重复设置它。只要没有其他方式输入代码(没有替代的main)，这就会起作用。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|149886|第二个最短的解决方案是扫描调用堆栈中的junit包，就像在Janning's+answer中一样。只要junit不把自己隐藏在另一个库和一个执行器后面，它就可以工作。|149887|依赖注入也会起作用，但在这种情况下，它只是一种设置本质上是全局标志的奇特方式。|149888|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/12717377/1981276^0|V|3|1B|6|31|4|0|T|G|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|D]|$9|X|A|Y|B|D]]|E|@]|F|$]]|$1|G|3|H|5|6|7|Z|8|@]|E|@$9|10|A|11|1|12]]|F|$]]|$1|I|3|J|5|6|7|13|8|@]|E|@]|F|$]]|$1|K|3|-4|5|6|7|14|8|@]|E|@]|F|$]]]|L|$M|$5|N|O|P|F|$Q|R]]]]

The shortest (least code) solution is to have a global flag that is set when tests are not running. You can then set it once in your <code>main()</code> (or similar entry point) instead of setting it repeatedly in setup methods of all test classes. This will work as long as there is no other way to enter the code (no alternate <code>main</code>).

The second shortest solution is to scan the call stack for junit package like in <a href="https://stackoverflow.com/a/12717377/1981276">Janning's answer</a>. This will work as far as junit doesn't hide itself behind another library and an executor.

Dependency injection will work too, but in this case it's just a fancy way to set what's essentially a global flag.

blocks|key|1262031|text|这对我很有效：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1262032|private+Boolean+isRunningTest+=+null;

private+boolean+isRunningTest()+{
++++if+(isRunningTest+==+null)+{
++++++++isRunningTest+=+true;
++++++++try+{
++++++++++++Class.forName("org.junit.Test");
++++++++}+catch+(ClassNotFoundException+e)+{
++++++++++++isRunningTest+=+false;
++++++++}
++++}
++++return+isRunningTest;
}|code-block|syntax|javascript|1262033|它可以在Maven测试中使用，也可以在Eclipse+IDE中使用，只要junit作为依赖项包含在作用域"test“中，例如：|1262034|<dependency>
++++<groupId>junit</groupId>
++++<artifactId>junit</artifactId>
++++<version>${junit.version}</version>
++++<scope>test</scope>
</dependency>|1262035|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|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

This has worked for me:

<pre><code>private Boolean isRunningTest = null;

private boolean isRunningTest() {
 if (isRunningTest == null) {
 isRunningTest = true;
 try {
 Class.forName("org.junit.Test");
 } catch (ClassNotFoundException e) {
 isRunningTest = false;
 }
 }
 return isRunningTest;
}
</code></pre>

It can be used in Maven tests, as well as inside the Eclipse IDE, as long as junit is included as a dependency with scope "test", eg:

<pre><code>&lt;dependency&gt;
 &lt;groupId&gt;junit&lt;/groupId&gt;
 &lt;artifactId&gt;junit&lt;/artifactId&gt;
 &lt;version&gt;${junit.version}&lt;/version&gt;
 &lt;scope&gt;test&lt;/scope&gt;
&lt;/dependency&gt;
</code></pre>

In my code I need to do certain fixes only when it is run inside a JUnit test. How can I find out if code is running inside a JUnit test or not? Is there something like JUnit.isRunning() == true ?

How can I find out if code is running inside a JUnit test or not?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

在我的代码中，只有当它在JUnit测试中运行时，我才需要进行某些修复。如何才能确定代码是否在JUnit测试中运行？有没有类似JUnit.isRunning() == true的东西？

问如何才能确定代码是否在JUnit测试中运行？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何才能确定代码是否在JUnit测试中运行？EN