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 7796803
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 1, 20262026-06-01T23:28:56+00:00 2026-06-01T23:28:56+00:00

how can I use JUnit to not terminate on assertion failures, but just log

  • 0

how can I use JUnit to not terminate on assertion failures, but just log them?

My goal is to fail if log messages exist, and print them out. Because I’d like to iterate over a big list, and want to know which elements fail.

How can I force JUnit to not break on failures?

ty

  • 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-06-01T23:28:58+00:00Added an answer on June 1, 2026 at 11:28 pm

    You can’t do what you want with standard JUnit, with your tests as they are. The problem is that assertXXX methods actually throw Exceptions (AssertionError), so you can’t use normal asserts and resume from the point after the exception has been thrown. JUnit catches these AssertIonErrors and does the right thing.

    One alternative is to use, as Ludwig suggested, the ErrorCollector rule, but it will mean rewriting a fair portion of your tests I would imagine.

    If your goal is to iterate over a large list, look at Parameterized. This allows you to iterate over single test method, with different data each time:

    @RunWith(Parameterized.class)
    public class FibonacciTest {
      @Parameters
      public static List<Object[]> data() {
        return Arrays.asList(new Object[][] {
          { 0, 0 }, { 1, 1 }, { 2, 1 }, { 3, 2 }, { 4, 3 }, { 5, 5 }, { 6, 8 }
        });
      }
    
      private int fInput;
    
      private int fExpected;
    
      public FibonacciTest(int input, int expected) {
        fInput= input;
        fExpected= expected;
      }
    
      @Test
      public void test() {
        assertEquals(fExpected, Fibonacci.compute(fInput));
      }
    }
    

    data() returns a list of Object[]. Each Object[] in the list is passed to the constructor of the test class. So a new instance of the test class is used for each entry in the list.

    The number of entries in the Object[] must correspond to the number of parameters to the constructor, and the types have to correspond as well.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

You can use e.g. JUnit to test the functionality of your library, but how
In JUnit you can use @Ignore before methods to tell the test runner to
I compile my programm against javaee-api. But for Junit testing I must use a
Maybe my question is a newbie one, but I can not really understand the
I can use FireFox and FireBug, in a pane, I can open a .css
I can use the PRINT statement in a stored procedure to debug my code.
I can use stat() to figure out what permissions the owner, group, or others
We can use solr range query like: http://localhost:8983/solr/select?q=queryStr&fq=x:[10 TO 100] AND y:[20 TO 300]
You can use the Filter property of a BindingSource to do SQL like filtering.
I can use ipcs(1) to list out the active shared memory objects on a

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.