Databases
StackOverflow2013
Postsdbo
POJUnit @Theory : is there a way to throw meaningful exception?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POJUnit @Theory : is there a way to throw meaningful exception?
    primarykey
    data
    text
    <p>I tried Junit @Theory test style recently : it's a really efficient way of testing. However, i not pleased with the exception that are thrown when a test fails. Example :</p> <pre><code>import static org.junit.Assert.assertEquals; import org.junit.experimental.theories.DataPoint; import org.junit.experimental.theories.Theories; import org.junit.experimental.theories.Theory; import org.junit.runner.RunWith; @RunWith(Theories.class) public class TheoryAndExceptionTest { @DataPoint public static String yesDataPoint = "yes"; @Theory public void sayNo(final String say) { assertEquals("no",say); } } </code></pre> <p>I expect this test to throw a <strong>descriptive</strong> exception, but instead of getting something like :</p> <pre><code>org.junit.ComparisonFailure: expected:&lt;'[no]'&gt; but was:&lt;'[yes]'&gt; </code></pre> <p>... I get this :</p> <pre><code>org.junit.experimental.theories.internal.ParameterizedAssertionError: sayNo(yes) at .... [23 lines of useless stack trace cut] ... Caused by: org.junit.ComparisonFailure: expected:&lt;'[no]'&gt; but was:&lt;'[yes]'&gt; .... </code></pre> <p>Is there a way to get rid of the 24 first lines that tell nothing about *<em>my</em>*test, except that yesDataPoint @DataPoint causes the failure ? That's an information i need, to know what is failing, but i really would like to know <em>how</em> it fails on the same time.</p> <p><strong>[edited]</strong></p> <p>I replaced org.fest.assertions usage by classic org.junit.Assert.assertEquals, to avoid confusion. Additionally, it's not related either with Eclipse : that long (useless/confusing) stack trace is what you get too when you run and fail a @Theory from the command line.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USOlivier
    1. USOlivier
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POJUnit @Theory : is there a way to throw meaningful exception?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POJUnit @Theory : is there a way to throw meaningful exception?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COHow are you getting these 23 lines before the "reaction on source"? In Eclipse for getting them from Failure Trace View, I have do go to the "reaction on source" you are looking for, "copy trace" , insert it somewhere and only then I can see all these lines.
      singulars
      1. POJUnit @Theory : is there a way to throw meaningful exception?
      1. USGangnus
    2. CO@Gangnus Eclipse filters out a lot of the stacktrace. Look in Workspace->Preferences->Java->JUnit. Which is why you don't see them in Eclipse.
      singulars
      1. POJUnit @Theory : is there a way to throw meaningful exception?
      1. USMatthew Farwell
    3. COSorry for my English. I already have them filtered away. What I say, I need to do something to see these extra lines. But thank you for the advice.
      singulars
      1. POJUnit @Theory : is there a way to throw meaningful exception?
      1. USGangnus
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload