[
https://issues.apache.org/jira/browse/SUREFIRE-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14574796#comment-14574796
]
ASF GitHub Bot commented on SUREFIRE-1067:
------------------------------------------
GitHub user Tibor17 opened a pull request:
https://github.com/apache/maven-surefire/pull/97
[SUREFIRE-1067] Nested causes conflated with wrapper exception
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Tibor17/maven-surefire s2
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/maven-surefire/pull/97.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #97
----
commit 59cc9f4e3d8738417cbf4ddfd639f912f9d68b7c
Author: Tibor17 <tibo...@lycos.com>
Date: 2015-06-05T16:38:25Z
[SUREFIRE-1067] Nested causes conflated with wrapper exception
----
> Nested causes conflated with wrapper exception
> ----------------------------------------------
>
> Key: SUREFIRE-1067
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1067
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Affects Versions: 2.13
> Environment: JDK 7u51 on Linux
> Reporter: Jesse Glick
> Assignee: Tibor Digana
> Priority: Critical
> Fix For: 2.19
>
>
> I created a simple Maven project containing just a test
> {code}
> package p;
> import java.io.IOException;
> import org.junit.Test;
> public class SomeTest {
> @Test public void t() throws Exception {
> try {
> m();
> } catch (RuntimeException x) {
> throw new IOException(x);
> }
> }
> private void m() {
> throw new UnsupportedOperationException();
> }
> }
> {code}
> If I run this using {{maven-surefire-plugin}} 2.12.4, I get a
> {{p.SomeTest.txt}} with the expected output:
> {code:none}
> -------------------------------------------------------------------------------
> Test set: p.SomeTest
> -------------------------------------------------------------------------------
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.037 sec <<<
> FAILURE!
> t(p.SomeTest) Time elapsed: 0.009 sec <<< ERROR!
> java.io.IOException: java.lang.UnsupportedOperationException
> at p.SomeTest.t(SomeTest.java:9)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
> Caused by: java.lang.UnsupportedOperationException
> at p.SomeTest.m(SomeTest.java:13)
> at p.SomeTest.t(SomeTest.java:7)
> ... 29 more
> {code}
> But if I use 2.13 or higher, I get
> {code:none}
> -------------------------------------------------------------------------------
> Test set: p.SomeTest
> -------------------------------------------------------------------------------
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.037 sec <<<
> FAILURE!
> t(p.SomeTest) Time elapsed: 0.009 sec <<< ERROR!
> java.io.IOException: java.lang.UnsupportedOperationException
> at p.SomeTest.m(SomeTest.java:13)
> at p.SomeTest.t(SomeTest.java:7)
> {code}
> which is missing the potentially crucial information about what threw the
> {{IOException}} and why. (Or if the wrapper exception does not follow the
> convention of appending {{": " + cause}} to its own {{message}}, the Surefire
> output would lack any information about the detail message in the original
> exception.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
