entityMap|blocks|key|5hgsi|text|你期望“期望的”如何工作？一个方法只能抛出一个异常。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4oert|您必须为该方法可能失败的每种方式编写不同的单元测试。因此，如果该方法合法地抛出了两个异常，那么您需要设置两个测试来强制该方法抛出每个异常。^0|0^^$0|$]|1|@$2|3|4|5|6|7|8|E|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|F|9|@]|A|@]|B|$]]]]

How would you expect to "expected"s to work? A method can only throw one exception.

You would have to write a different unit test for each way the method can fail. So if the method legitimately throw two exceptions then you need two tests set up to force the method of throwing each exception.

entityMap|blocks|key|acmb5|text|你真的想让测试一个并对其进行测试。如果您不确定将抛出哪个异常，那么对我来说，这听起来不是一个好的测试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1hnfo|例如(伪代码)|5t00q|try+{
+++badOperation();
+++///+looks+like+we+succeeded.+Not+good!+Fail+the+test
+++fail();
}
catch+(ExpectedException+e)+{
+++//+that's+fine
}
catch+(UnexpectedException+e)+{
+++//+that's+NOT+fine.+Fail+the+test
}|code-block|syntax|javascript|57q8p|因此，如果你想测试你的方法抛出了两个不同的异常(对于两组输入)，那么你需要两个测试。^0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|L|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|M|9|@]|A|@]|B|$]]|$2|E|4|F|6|G|8|N|9|@]|A|@]|B|$H|I]]|$2|J|4|K|6|7|8|O|9|@]|A|@]|B|$]]]]

You really want the test to do one thing, and to test for that. If you're not sure as to which exception is going to be thrown, that doesn't sound like a good test to me.

e.g. (in pseudo-code)

<pre><code>try {
 badOperation();
 /// looks like we succeeded. Not good! Fail the test
 fail();
}
catch (ExpectedException e) {
 // that's fine
}
catch (UnexpectedException e) {
 // that's NOT fine. Fail the test
}
</code></pre>

so if you want to test that your method throws 2 different exceptions (for 2 sets of inputs), then you'll need 2 tests.

entityMap|blocks|key|3n7l2|text|尽可能保持测试的简单和简短。JUnit-Test的目的是只测试一种简单的功能或一种单一的失败方式。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2l2ft|实际上，为了安全起见，您应该至少为每种可能的执行方式创建一个测试。|duea4|通常，这并不总是可能的，因为如果你有一个分析字符串的方法，那么有太多可能的字符串组合，以至于你不能涵盖所有的东西。|a65qf|保持简短和简单。|fag2o|对于一种方法，您可以轻松地使用30-40种测试方法……这真的很重要吗？|316er|问候^0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|M|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|N|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|O|9|@]|A|@]|B|$]]|$2|G|4|H|6|7|8|P|9|@]|A|@]|B|$]]|$2|I|4|J|6|7|8|Q|9|@]|A|@]|B|$]]|$2|K|4|L|6|7|8|R|9|@]|A|@]|B|$]]]]

Keep the tests as simple and short as possible. The intention of a JUnit-Test is to test only one simple functionality or one single way of failure.

Indeed, to be safe, you should create at least one test for every possible execution way.

Normally, this is not always possible because if you have a method that analyses a string, there are so many possible string combinations that you cannot cover everything.

Keep it short and simple.

You can have 30-40 testing methods for one single method easily... does it really matter?

Regards

entityMap|0|type|LINK|mutability|MUTABLE|data|url|http://greenbar.saff.net/?p=17|1|http://greenbar.saff.net/?p=18|blocks|key|3pv47|text|对于注释，这是不可能的。|unstyled|depth|inlineStyleRanges|entityRanges|1jgfj|在JUnit+4.7中，您可以使用新的ExpectedException规则|offset|length|style|CODE|1urf1|public+static+class+HasExpectedException+{
++++@Interceptor
++++public+ExpectedException+thrown=+new+ExpectedException();

++++@Test
++++public+void+throwsNothing()+{
++++}

++++@Test
++++public+void+throwsNullPointerException()+{
+++++++++thrown.expect(NullPointerException.class);
+++++++++throw+new+NullPointerException();
++++}

++++@Test
++++public+void+throwsNullPointerExceptionWithMessage()+{
++++++++thrown.expect(NullPointerException.class);
++++++++thrown.expectMessage("happened?");
++++++++throw+new+NullPointerException("What+happened?");
++++}
}|code-block|syntax|javascript|8i9g8|更多信息请参阅|e7mqb|JUnit+4.7：拦截器：预期异常|unordered-list-item|62ijc|JUnit+4.7+中的规则|p1vd|如果您无法更新到JUnit+4.7，则必须编写表单的裸单元测试|fo428|public+test()+{
++++try+{
++++++++methodCall();+//+should+throw+Exception
++++++++fail();
++++}
++++catch+(Exception+ex)+{
++++++++assert((ex+instanceof+A)+%7C%7C+(ex+instanceof+B)+%7C%7C+...etc...);
++++++++...
++++}|2teid|}^0|0|J|H|0|0|0|0|I|0|0|0|E|1|0|0|0^^$0|$1|$2|3|4|5|6|$7|8]]|9|$2|3|4|5|6|$7|A]]]|B|@$C|D|E|F|2|G|H|18|I|@]|J|@]|6|$]]|$C|K|E|L|2|G|H|19|I|@$M|1A|N|1B|O|P]]|J|@]|6|$]]|$C|Q|E|R|2|S|H|1C|I|@]|J|@]|6|$T|U]]|$C|V|E|W|2|G|H|1D|I|@]|J|@]|6|$]]|$C|X|E|Y|2|Z|H|1E|I|@]|J|@$M|1F|N|1G|C|1H]]|6|$]]|$C|10|E|11|2|Z|H|1I|I|@]|J|@$M|1J|N|1K|C|1L]]|6|$]]|$C|12|E|13|2|G|H|1M|I|@]|J|@]|6|$]]|$C|14|E|15|2|S|H|1N|I|@]|J|@]|6|$T|U]]|$C|16|E|17|2|G|H|1O|I|@]|J|@]|6|$]]]]

This is not possible with the annotation.

With JUnit 4.7 you can use the new <code>ExpectedException</code> rule

<pre><code>public static class HasExpectedException {
 @Interceptor
 public ExpectedException thrown= new ExpectedException();

 @Test
 public void throwsNothing() {
 }

 @Test
 public void throwsNullPointerException() {
 thrown.expect(NullPointerException.class);
 throw new NullPointerException();
 }

 @Test
 public void throwsNullPointerExceptionWithMessage() {
 thrown.expect(NullPointerException.class);
 thrown.expectMessage("happened?");
 throw new NullPointerException("What happened?");
 }
}
</code></pre>

More see

<ul>
<li><a href="http://greenbar.saff.net/?p=17" rel="noreferrer">JUnit 4.7: Interceptors: expected exceptions</a></li>
<li><a href="http://greenbar.saff.net/?p=18" rel="noreferrer">Rules in JUnit 4.7</a></li>
</ul>

<hr>

If updating to JUnit 4.7 is not possible for you, you have to write a bare unit test of the form

<pre><code>public test() {
 try {
 methodCall(); // should throw Exception
 fail();
 }
 catch (Exception ex) {
 assert((ex instanceof A) || (ex instanceof B) || ...etc...);
 ...
 }
</code></pre>

}

entityMap|0|type|LINK|mutability|MUTABLE|data|url|http://code.google.com/p/catch-exception/|blocks|key|c1h80|text|使用catch-exception|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|65ob1|//+test+
public+void+testDo()+{

+++//+obj.do(1)+must+throw+either+A+or+B
+++catchException(obj).do(1);
+++assert+caughtException()+instanceof+A
+++++++%7C%7C+caughtException()+instanceof+B;

+++//+obj.do(2)+must+throw+A+but+not+SubclassOfA
+++catchException(obj).do(2);
+++assert+caughtException()+instanceof+A
+++++++&&+!(caughtException()+instanceof+SubclassOfA);

}|code-block|syntax|javascript^0|2|F|0|0^^$0|$1|$2|3|4|5|6|$7|8]]]|9|@$A|B|C|D|2|E|F|P|G|@]|H|@$I|Q|J|R|A|S]]|6|$]]|$A|K|C|L|2|M|F|T|G|@]|H|@]|6|$N|O]]]]

Use <a href="http://code.google.com/p/catch-exception/" rel="nofollow">catch-exception</a>:

<pre><code>// test 
public void testDo() {

 // obj.do(1) must throw either A or B
 catchException(obj).do(1);
 assert caughtException() instanceof A
 || caughtException() instanceof B;

 // obj.do(2) must throw A but not SubclassOfA
 catchException(obj).do(2);
 assert caughtException() instanceof A
 &amp;&amp; !(caughtException() instanceof SubclassOfA);

}
</code></pre>

entityMap|blocks|key|3pcrj|text|@Test(expected=Exception.class)|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|js|eos7n|这将抛出所有可能的异常。|unstyled^0|0^^$0|$]|1|@$2|3|4|5|6|7|8|H|9|@]|A|@]|B|$C|D]]|$2|E|4|F|6|G|8|I|9|@]|A|@]|B|$]]]]

<pre><code>@Test(expected=Exception.class)
</code></pre>

This will throw all possible exceptions.

entityMap|blocks|key|bf3lq|text|虽然这在JUnit+4中是不可能的，但它是如果您切换到TestNG，这是可能的，它允许您编写|type|unstyled|depth|inlineStyleRanges|entityRanges|data|c3sba|@Test(expectedExceptions+=+{IllegalArgumentException.class,+NullPointerException.class})|code-block|syntax|js^0|0^^$0|$]|1|@$2|3|4|5|6|7|8|H|9|@]|A|@]|B|$]]|$2|C|4|D|6|E|8|I|9|@]|A|@]|B|$F|G]]]]

Although this is not possible with JUnit 4, it is possible if you switch to TestNG, which allows you to write 

<pre><code>@Test(expectedExceptions = {IllegalArgumentException.class, NullPointerException.class})
</code></pre>

Is it possible to test for multiple exceptions in a single JUnit unit test? I know for a single exception one can use, for example

<pre><code> @Test(expected=IllegalStateException.class)
</code></pre>

Now, if I want to test for another exception (say, NullPointerException), can this be done in the same annotation, a different annotation or do I need to write another unit test completely?

Testing for multiple exceptions with JUnit 4 annotations

单元测试

 是否可以在单个JUnit单元测试中测试多个异常？我知道有一个例外可以使用，例如 @Test(expected=IllegalStateException.class) 现在，如果我想测试另一个异常(比如NullPointerException)，是否可以在相同的注释、不同的注释中完成这项工作，或者我是否需要完全编写另...

问使用JUnit 4注释测试多个异常
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用JUnit 4注释测试多个异常EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用JUnit 4注释测试多个异常
EN