Java中如何验证请求异常,在Java中如何使用JUnit验证抛出的异常?

When writing unit tests for a Java API there may be circumstances where you want to perform more detailed validation of an exception. I.e. more than is offered by the @test annotation offered by JUnit.

For example, consider an class that should catch an exception from some other Interface, wrap that exception and throw the wrapped exception. You may want to verify:

The exact method call that throws the wrapped exception.

That the wrapper exception has the original exception as its cause.

The message of the wrapper exception.

The main point here is that you want to be perf additional validation of an exception in a unit test (not a debate about whether you should verify things like the exception message).

What's a good approach for this?

解决方案

In JUnit 4 it can be easily done using ExpectedException rule.

Here is example from javadocs:

// These tests all pass.

public static class HasExpectedException {

@Rule

public ExpectedException thrown = ExpectedException.none();

@Test

public void throwsNothing() {

// no exception expected, none thrown: passes.

}

@Test

public void throwsNullPointerException() {

thrown.expect(NullPointerException.class);

throw new NullPointerException();

}

@Test

public void throwsNullPointerExceptionWithMessage() {

thrown.expect(NullPointerException.class);

thrown.expectMessage("happened?");

thrown.expectMessage(startsWith("What"));

throw new NullPointerException("What happened?");

}

}

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值