blocks|key|863480|text|您是否可以将“系统退出”抽象为一个新的依赖项，以便在您的测试中只有一个假的，它记录了exit已被调用的事实(以及值)，但在实际应用程序中使用调用System.exit的实现？|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|863481|entityMap^0|20|B|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

Could you abstract out the "system exiting" into a new dependency, so that in your tests you could just have a fake which records the fact that exit has been called (and the value), but use an implementation which calls <code>System.exit</code> in the real application?

blocks|key|863506|text|我如何处理这个问题是安装一个安全管理器，它在调用System.exit时抛出异常。然后是捕获异常的代码，并且不会导致测试失败。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|863507|public+class+NoExitSecurityManager
++++extends+java.rmi.RMISecurityManager
{
++++private+final+SecurityManager+parent;

++++public+NoExitSecurityManager(final+SecurityManager+manager)
++++{
++++++++parent+=+manager;
++++}

++++public+void+checkExit(int+status)
++++{
++++++++throw+new+AttemptToExitException(status);
++++}

++++public+void+checkPermission(Permission+perm)
++++{
++++}
}|code-block|syntax|javascript|863508|然后在代码中，类似于：|863509|catch(final+Throwable+ex)
{
++++final+Throwable+cause;

++++if(ex.getCause()+==+null)
++++{
++++++++cause+=+ex;
++++}
++++else
++++{
++++++++cause+=+ex.getCause();
++++}

++++if(cause+instanceof+AttemptToExitException)
++++{
++++++++status+=+((AttemptToExitException)cause).getStatus();
++++}
++++else
++++{
++++++++throw+cause;
++++}
}

assertEquals("System.exit+must+be+called+with+the+value+of+"+%2B+expectedStatus,+expectedStatus,+status);|863510|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|$]]

How I deal with that is to install a security manager that throws an exception when System.exit is called. Then there is code that catches the exception and doesn't fail the test.

<pre><code>public class NoExitSecurityManager
 extends java.rmi.RMISecurityManager
{
 private final SecurityManager parent;

 public NoExitSecurityManager(final SecurityManager manager)
 {
 parent = manager;
 }

 public void checkExit(int status)
 {
 throw new AttemptToExitException(status);
 }

 public void checkPermission(Permission perm)
 {
 }
}
</code></pre>

And then in the code, something like:

<pre><code>catch(final Throwable ex)
{
 final Throwable cause;

 if(ex.getCause() == null)
 {
 cause = ex;
 }
 else
 {
 cause = ex.getCause();
 }

 if(cause instanceof AttemptToExitException)
 {
 status = ((AttemptToExitException)cause).getStatus();
 }
 else
 {
 throw cause;
 }
}

assertEquals("System.exit must be called with the value of " + expectedStatus, expectedStatus, status);
</code></pre>

blocks|key|2480393|text|库System+Rules有一个名为ExpectedSystemExit的JUnit规则。使用此规则，您可以测试调用System.exit(...)的代码：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2480394|public+class+MyTest+{
++++@Rule
++++public+final+ExpectedSystemExit+exit+=+ExpectedSystemExit.none();

++++@Test
++++public+void+systemExitWithArbitraryStatusCode()+{
++++++++exit.expectSystemExit();
++++++++/*+the+code+under+test,+which+calls+System.exit(...)
+++++++++*+with+an+arbitrary+status
+++++++++*/
++++}

++++@Test
++++public+void+systemExitWithSelectedStatusCode0()+{
++++++++exit.expectSystemExitWithStatus(0);
++++++++//the+code+under+test,+which+calls+System.exit(0)
++++}
}|code-block|syntax|javascript|2480395|系统规则至少需要JUnit+4.9。|2480396|完全公开:我是系统规则的作者。|2480397|entityMap|0|LINK|mutability|MUTABLE|url|http://stefanbirkner.github.io/system-rules/^0|1|C|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|Z|8|@]|9|@]|C|$]]|$1|K|3|L|5|6|7|10|8|@]|9|@]|C|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]]]

The library <a href="http://stefanbirkner.github.io/system-rules/" rel="nofollow noreferrer">System Rules</a> has a JUnit rule called ExpectedSystemExit. With this rule you are able to test code, that calls System.exit(...):
<pre><code>public class MyTest {
 @Rule
 public final ExpectedSystemExit exit = ExpectedSystemExit.none();

 @Test
 public void systemExitWithArbitraryStatusCode() {
 exit.expectSystemExit();
 /* the code under test, which calls System.exit(...)
 * with an arbitrary status
 */
 }

 @Test
 public void systemExitWithSelectedStatusCode0() {
 exit.expectSystemExitWithStatus(0);
 //the code under test, which calls System.exit(0)
 }
}
</code></pre>
System Rules needs at least JUnit 4.9.
Full disclosure: I'm the author of System Rules.

blocks|key|4556547|text|如果有人需要JUnit+5的这个功能，我已经written+an+extension来做了。这是一个简单的注解，您可以用来告诉您的测试用例期望和退出状态代码或特定的退出状态代码。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4556548|例如，任何退出代码都可以：|4556549|public+class+MyTestCases+{+

++++@Test
++++@ExpectSystemExit
++++public+void+thatSystemExitIsCalled()+{
++++++++System.exit(1);
++++}
}|code-block|syntax|javascript|4556550|如果我们想要查找特定的代码：|4556551|public+class+MyTestCases+{

++++@Test
++++@ExpectSystemExitWithStatus(1)
++++public+void+thatSystemExitIsCalled()+{
++++++++System.exit(1);
++++}
}|4556552|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/tginsberg/junit5-system-exit^0|M|K|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]]|C|$]]|$1|D|3|E|5|6|7|10|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|11|8|@]|9|@]|C|$I|J]]|$1|K|3|L|5|6|7|12|8|@]|9|@]|C|$]]|$1|M|3|N|5|H|7|13|8|@]|9|@]|C|$I|J]]|$1|O|3|-4|5|6|7|14|8|@]|9|@]|C|$]]]|P|$Q|$5|R|S|T|C|$U|V]]]]

If anybody needs this functionality for JUnit 5, I've <a href="https://github.com/tginsberg/junit5-system-exit" rel="nofollow noreferrer">written an extension</a> to do this. This is a simple annotation you can use to tell your test case to expect and exit status code or a specific exit status code.

For example, any exit code will do:

<pre><code>public class MyTestCases { 

 @Test
 @ExpectSystemExit
 public void thatSystemExitIsCalled() {
 System.exit(1);
 }
}
</code></pre>

If we want to look for a specific code:

<pre><code>public class MyTestCases {

 @Test
 @ExpectSystemExitWithStatus(1)
 public void thatSystemExitIsCalled() {
 System.exit(1);
 }
}
</code></pre>

I am implementing some tests for an existing Java Swing application, so that I can safely refactor and extend the code without breaking anything. I started with some unit tests in JUnit, since that seems the simplest way to get started, but now my priority is to create some end-to-end tests to exercise the application as a whole.

I am starting the application afresh in each test by putting each test method in a separate test case, and using the <code>fork="yes"</code> option in Ant's <code>junit</code> task. However, some of the use cases I would like to implement as tests involve the user exiting the application, which results in one of the methods calling System.exit(0). This is regarded by JUnit as an error: <code>junit.framework.AssertionFailedError: Forked Java VM exited abnormally</code>.

Is there a way to tell JUnit that exiting with a return code of zero is actually OK?

Dealing with System.exit(0) in JUnit tests

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我正在为现有的Java Swing应用程序实现一些测试，这样我就可以安全地重构和扩展代码，而不会破坏任何东西。我从JUnit中的一些单元测试开始，因为这似乎是最简单的入门方法，但现在我的首要任务是创建一些端到端测试来作为一个整体来测试应用程序。我在每次测试中重新启动应用程序，将每个测试方法放在单独的测试用例中，并在An...

问在JUnit测试中处理System.exit(0)
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在JUnit测试中处理System.exit(0)EN