Over a million developers have joined DZone.

Testing Exceptions on the NetBeans Platform on Maven

· Java Zone

Microservices! They are everywhere, or at least, the term is. When should you use a microservice architecture? What factors should be considered when making that decision? Do the benefits outweigh the costs? Why is everyone so excited about them, anyway?  Brought to you in partnership with IBM.

Testing for expected exceptions does not work correctly in junit <= 4.5

Junit4 provided the functionality to test for expected exceptions. Expected exceptions can be tested with the method annotation @Test:

public void testSomeException() throws SomeException {
// some code that is expected to throw SomeException

However, in junit version < 4.5  this does not work like it should (not at all, tests will fail if expected exception gets thrown). The Maven module for the NetBeans extention for junit has a dependency on a wrapper around junit version 4.5. To be able to test for exceptions, a higher version of junit is needed. This is easily achieved by excluding the dependency on the junit 4.5 wrapper and explicitly declaring a dependency on a junit with a higher version (like 4.8.2 in our case).




Discover how the Watson team is further developing SDKs in Java, Node.js, Python, iOS, and Android to access these services and make programming easy. Brought to you in partnership with IBM.


Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}