blocks|key|366207|text|你确定你告诉它去期待异常吗？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|366208|对于较新的junit+(>=+4.7)，您可以使用(来自here)|offset|length|366209|@Rule
public+ExpectedException+exception+=+ExpectedException.none();

@Test
public+void+testRodneCisloRok(){
++++exception.expect(IllegalArgumentException.class);
++++exception.expectMessage("error1");
++++new+RodneCislo("891415",dopocitej("891415"));
}|code-block|syntax|javascript|366210|对于较旧的junit，如下所示：|366211|@Test(expected+=+ArithmeticException.class)++
public+void+divisionWithException()+{++
++int+i+=+1/0;
}|366212|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/4489801/junit-test-analysing-expected-exceptions^0|0|S|4|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@$D|Y|E|Z|1|10]]|A|$]]|$1|F|3|G|5|H|7|11|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|12|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|13|8|@]|9|@]|A|$I|J]]|$1|O|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]]]

are you sure you told it to expect the exception?

for newer junit (>= 4.7), you can use something like (from <a href="https://stackoverflow.com/questions/4489801/junit-test-analysing-expected-exceptions">here</a>)

<pre><code>@Rule
public ExpectedException exception = ExpectedException.none();

@Test
public void testRodneCisloRok(){
 exception.expect(IllegalArgumentException.class);
 exception.expectMessage("error1");
 new RodneCislo("891415",dopocitej("891415"));
}
</code></pre>

and for older junit, this:

<pre><code>@Test(expected = ArithmeticException.class) 
public void divisionWithException() { 
 int i = 1/0;
}
</code></pre>

blocks|key|366237|text|如果您的构造函数与下面的构造函数类似：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|366238|public+Example(String+example)+{
++++if+(example+==+null)+{
++++++++throw+new+NullPointerException();
++++}
++++//do+fun+things+with+valid+example+here
}|code-block|syntax|javascript|366239|然后，当您运行此JUnit测试时，您将得到一个绿色条：|366240|@Test(expected+=+NullPointerException.class)
public+void+constructorShouldThrowNullPointerException()+{
++++Example+example+=+new+Example(null);
}|366241|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|$]]

If your constructor is similar to this one:

<pre><code>public Example(String example) {
 if (example == null) {
 throw new NullPointerException();
 }
 //do fun things with valid example here
}
</code></pre>

Then, when you run this JUnit test you will get a green bar:

<pre><code>@Test(expected = NullPointerException.class)
public void constructorShouldThrowNullPointerException() {
 Example example = new Example(null);
}
</code></pre>

blocks|key|366261|text|使用ExpectedException规则(版本4.7)的一个优点是您可以测试异常消息，而不仅仅是预期的异常。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|366262|使用Matcher，您可以测试您感兴趣的消息部分：|366263|exception.expectMessage(containsString("income:+-1000.0"));|code-block|syntax|javascript|366264|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|$]]

An adventage of use ExpectedException Rule (version 4.7) is that you can test exception message and not only the expected exception.

And using Matchers, you can test the part of message you are interested:

<pre><code>exception.expectMessage(containsString("income: -1000.0"));
</code></pre>

blocks|key|148090|text|尽管@Test(expected+=+MyException.class)和ExpectedException+rule是非常好的选择，但在某些情况下，JUnit3样式的异常捕获仍然是最好的方法：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|148091|@Test+public+void+yourTest()+{
++try+{
++++systemUnderTest.doStuff();
++++fail("MyException+expected.");
++}+catch+(MyException+expected)+{

++++//+Though+the+ExpectedException+rule+lets+you+write+matchers+about
++++//+exceptions,+it+is+sometimes+useful+to+inspect+the+object+directly.

++++assertEquals(1301,+expected.getMyErrorCode());
++}

++//+In+both+@Test(expected=...)+and+ExpectedException+code,+the
++//+exception-throwing+line+will+be+the+last+executed+line,+because+Java+will
++//+still+traverse+the+call+stack+until+it+reaches+a+try+block--which+will+be
++//+inside+the+JUnit+framework+in+those+cases.+The+only+way+to+prevent+this
++//+behavior+is+to+use+your+own+try+block.

++//+This+is+especially+useful+to+test+the+state+of+the+system+after+the
++//+exception+is+caught.

++assertTrue(systemUnderTest.isInErrorState());
}|code-block|syntax|javascript|148092|另一个声称在这里提供帮助的库是catch-exception；然而，截至2014年5月，该项目似乎处于维护模式(已被Java8淘汰)，并且很像Mockito+catch-exception只能操作非final方法。|148093|entityMap|0|LINK|mutability|MUTABLE|url|http://junit-team.github.io/junit/javadoc/4.10/org/junit/rules/ExpectedException.html|1|https://code.google.com/p/catch-exception/^0|2|Z|12|M|0|0|0|2R|5|F|F|1|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@$9|Z|A|10|1|11]]|E|$]]|$1|F|3|G|5|H|7|12|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|13|8|@$9|14|A|15|B|C]]|D|@$9|16|A|17|1|18]]|E|$]]|$1|M|3|-4|5|6|7|19|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]|U|$5|P|Q|R|E|$S|V]]]]

Though <code>@Test(expected = MyException.class)</code> and the <a href="http://junit-team.github.io/junit/javadoc/4.10/org/junit/rules/ExpectedException.html" rel="noreferrer">ExpectedException rule</a> are very good choices, there are some instances where the JUnit3-style exception catching is still the best way to go:

<pre><code>@Test public void yourTest() {
 try {
 systemUnderTest.doStuff();
 fail("MyException expected.");
 } catch (MyException expected) {

 // Though the ExpectedException rule lets you write matchers about
 // exceptions, it is sometimes useful to inspect the object directly.

 assertEquals(1301, expected.getMyErrorCode());
 }

 // In both @Test(expected=...) and ExpectedException code, the
 // exception-throwing line will be the last executed line, because Java will
 // still traverse the call stack until it reaches a try block--which will be
 // inside the JUnit framework in those cases. The only way to prevent this
 // behavior is to use your own try block.

 // This is especially useful to test the state of the system after the
 // exception is caught.

 assertTrue(systemUnderTest.isInErrorState());
}
</code></pre>

Another library that claims to help here is <a href="https://code.google.com/p/catch-exception/" rel="noreferrer">catch-exception</a>; however, as of May 2014, the project appears to be in maintenance mode (obsoleted by Java 8), and much like Mockito catch-exception can only manipulate non-<code>final</code> methods.

I'm really new to java. 

I'm running some JUnit tests on a constructor. The constructor is such that if it is given a null or an empty string for one of its parameters, it's supposed to throw an exception. 

When I test this constructor in JUnit with a null or an empty string parameter, I get a red bar, even though I'm almost 100% sure that the constructor method does indeed throw an exception when such parameters are passed in to it. 

Shouldn't there be a green bar in JUnit if the method throws an exception the way it is supposed to? Or is it that when you are supposed to get a red bar when the exception throwing works the way it is supposed to?

JUnit Testing Exceptions

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我对java还是个新手。我正在构造器上运行一些JUnit测试。构造函数是这样的，如果它的一个参数被赋予一个null或空字符串，它就会抛出一个异常。当我在JUnit中使用null或空字符串参数测试此构造函数时，我得到了一个红色条，即使我几乎100%地确定构造函数方法在传入此类参数时确实会抛出异常。如果该方法按照预期的方式...

问JUnit测试异常
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问JUnit测试异常EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问JUnit测试异常
EN