blocks|key|1177703|text|看起来失败是因为你的测试用例失败了--也就是说你的断言是不正确的。错误是在尝试实际运行测试异常时发生的意外错误，等等。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1177704|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|$]]

It seems that failures are when your test cases fail – i.e. your assertions are incorrect. Errors are unexpected errors that occur while trying to actually run the test – exceptions, etc.

blocks|key|963525|text|如果您的测试抛出了一个异常，而该异常没有通过Junit中的断言框架冒泡出来，那么它会被报告为一个错误。例如，NullPointer或ClassNotFound异常将报告错误：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|963526|String+s+=+null;
s.trim();|code-block|syntax|javascript|963527|或,|963528|try+{

++++//+your+code
}+catch(Exception+e)+{
++++//+log+the+exception
++++throw+new+MyException(e);
}|963529|话虽如此，以下代码将报告失败：|963530|Assert.fail("Failure+here");|963531|963532|Assert.assertEquals(1,+2);|963533|或者甚至是：|963534|throw+new+AssertionException(e);|963535|这取决于您正在使用的Junit版本。Junit+4-将区分故障和错误，但Junit+4将其简化为仅故障。|963536|下面的链接提供了更多有趣的输入：|963537|http://www.devx.com/Java/Article/31983/1763/page/2|offset|length|963538|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|0|0|0|0|0|0|0|0|0|0|1E|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|1B|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|1C|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|1D|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|1E|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|1F|8|@]|9|@]|A|$E|F]]|$1|O|3|H|5|6|7|1G|8|@]|9|@]|A|$]]|$1|P|3|Q|5|D|7|1H|8|@]|9|@]|A|$E|F]]|$1|R|3|S|5|6|7|1I|8|@]|9|@]|A|$]]|$1|T|3|U|5|D|7|1J|8|@]|9|@]|A|$E|F]]|$1|V|3|W|5|6|7|1K|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|1L|8|@]|9|@]|A|$]]|$1|Z|3|10|5|6|7|1M|8|@]|9|@$11|1N|12|1O|1|1P]]|A|$]]|$1|13|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]]|14|$15|$5|16|17|18|A|$19|10]]]]

If your test throws an exception which does not get bubbled up through the Assertion framework in Junit, it gets reported as an error. For example, a NullPointer, or a ClassNotFound exception will report an error:

<pre><code>String s = null;
s.trim();
</code></pre>

or,

<pre><code>try {

 // your code
} catch(Exception e) {
 // log the exception
 throw new MyException(e);
}
</code></pre>

Having said that, the following will report a failure:

<pre><code>Assert.fail("Failure here");
</code></pre>

or,

<pre><code>Assert.assertEquals(1, 2);
</code></pre>

or even:

<pre><code>throw new AssertionException(e);
</code></pre>

It depends on the Junit version you are using. Junit 4- will make the distinction between a failure and an error, but Junit 4 simplifies it as failures only.

Following link provides more interesting inputs:

<a href="http://www.devx.com/Java/Article/31983/1763/page/2" rel="noreferrer">http://www.devx.com/Java/Article/31983/1763/page/2</a>

blocks|key|1177812|text|您说得对，失败来自JUnit断言方法抛出的AssertionErrors，或者抛出AssertionError，或者抛出您在@Test注释中声明的异常，而错误来自其他意外的异常。但它们之间有一个重要的区别：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1177813|失败意味着您的测试运行正常，并且确定了代码中的缺陷。|1177814|错误可能意味着您的代码中存在bug，但您甚至没有对其进行测试。这也可能意味着bug存在于测试本身。|1177815|简而言之，失败意味着您需要重写正在测试的代码。错误意味着它可能是您需要重写的单元测试。这可能意味着即使失败出现在您的代码中，例如NullPointerException，因为您检测到了一个您甚至没有测试过的缺陷，所以测试它可能是明智的。|1177816|entityMap^0|1Q|5|0|0|0|1S|K|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Q|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|R|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|L|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|M|$]]

You are right that failures come from the AssertionErrors thrown by the JUnit assertion methods, or by throwing an AssertionError, or by throwing an exception that you declared in your <code>@Test</code> annotation, and Errors come from other, unexpected Exceptions. But there's an important distinction between them: 

A failure means your test ran correctly, and identified a defect in your code.

An error could mean a bug in your code, but one that you weren't even testing for. It could also mean that the bug is in the test itself.

In short, a failure means you need to rewrite the code that is being tested. An error means that it may be the unit test that you need to rewrite. It may mean this even if the failure was in your code, such as a <code>NullPointerException</code>, because you detected a flaw that you weren't even testing for, so it might be wise to test for that.

I'm running JUnit tests on a large code base, and I've been realizing that sometimes I get "Errors" while other times I get "Failures". What's the difference?

What's the difference between failure and error in JUnit?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我在一个大型代码库上运行JUnit测试，并且我已经意识到，有时我会遇到“错误”，而有时我会遇到“失败”。有什么关系呢？

问JUnit中失败和错误的区别是什么？
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问JUnit中失败和错误的区别是什么？EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问JUnit中失败和错误的区别是什么？
EN