Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7060927
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 28, 20262026-05-28T04:24:42+00:00 2026-05-28T04:24:42+00:00

I have a test that expects a particular exception, for example: @Test(expected=MyException.class) public void

  • 0

I have a test that expects a particular exception, for example:

@Test(expected=MyException.class)
public void testMyMethod(){
    myMethod();
}

The myMethod() method actually throws a subclass of MyException, lets call it MySubclassException.

Is there anyway to define my test using the @Test annotation to accept subclasses of MyException as well as the class itself?

I know that I could simply write the test checking logic myself without using expected by catching the exception and setting a flag, but I was wondering whether or not JUnit already supported matching exception subclasses.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-28T04:24:43+00:00Added an answer on May 28, 2026 at 4:24 am

    This is already handled for you by the framework

    Let’s take a small example (very bad code):
    import static org.junit.Assert.*;

    import org.junit.Test;
    
    
    public class TestExpect {
    
    @Test(expected=MyException.class)
    public void test() throws MyException {
        new Foo().foo();
    }
    
    }
    

    With 2 exception classes MyException and MyExtendedException inheriting from the previous one and a simple Foo class like this one:

    public class Foo {
    
    public void foo() throws MyException{
        throw new MyExtendedException();
    }
    }
    

    Launching the test using the Eclipse runner prints a green bar because the test raises one instance of Myexception (is a relationship in POO)

    If you prefer to read source code this is an exxcerpt from the Junit source code (ExpectException.java):

       @Override
        public void evaluate() throws Exception {
            boolean complete = false;
            try {
                fNext.evaluate();
                complete = true;
            } catch (AssumptionViolatedException e) {
                throw e;
            } catch (Throwable e) {
                if (!fExpected.isAssignableFrom(e.getClass())) {
                    String message= "Unexpected exception, expected<"
                                + fExpected.getName() + "> but was<"
                                + e.getClass().getName() + ">";
                    throw new Exception(message, e);
                }
            }
            if (complete)
                throw new AssertionError("Expected exception: "
                        + fExpected.getName());
        }
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a method that I want to test which expects an IEnumerable<T> as
I have a unit test that creates a mock calls my method to be
I have a unit test that tests if an Exception is throw, but this
I have this JUnit test that I need help developing a Interface and Class
So I have this builder that runs a buildClass method which should be public,
I have a number of test classes and methods that copy a particular directory
I have a JUnit test that tests adding Strings to a Dictionary custom type.
I have a unit test that works fine locally but when uploaded to TeamCity
I have a test file that contains tests taking quite a lot of time
I have a test file that has many lines, each line looks something like:

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.