AssumptionViolatedException erroneously initializes cause to "null"

[mmichaelis]

Digging into the code of AssumptionViolatedException you will find:

public AssumptionViolatedException(Object value, Matcher<?> matcher) {
    super(value instanceof Throwable ? (Throwable) value : null);
    fValue= value;
    fMatcher= matcher;
}

According the documentation of "cause" in java.lang.Throwable this states that there is no (known) cause for this exception. If instead the cause is not yet initialized the cause should point to this - which is the initial value in Throwable.

For the work I am doing I need to specify a message and a cause. Having the current API this is not possible:

• There is no 2-arg constructor with message and cause
• initCause() cannot be called because Throwable does not allow to set the cause twice (and it got set to null before)

For me the solution would be sufficient to introduce a constructor AssumptionViolatedException(message, cause). But the real problem (from my point of view) is the erroneous initialization with null.

[mmichaelis]

This workaround works for me for now:

throw new AssumptionViolatedException(message) {
  @Override
  public Throwable getCause() {
    return lastException;
  }
};

[priav03]

Is this still an open issue? How can I help?

[kcooney]

It looks like it is still open, and should be an easy and safe enough fix to squeeze into 4.12.

[marcin-lawrowski]

So, the first constructor in org.junit.internal.AssumptionViolatedException class should be fixed to initialize superclass with "this" instead of "null" ?

[kcooney]

I believe the first constructor should init the cause via initCause()

[marcphilipp]

Fixed by #985.