[JBoss JIRA] (ARQ-2010) Report first Exception caught in TestRunner
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/ARQ-2010?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen updated ARQ-2010:
-------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Report first Exception caught in TestRunner
> -------------------------------------------
>
> Key: ARQ-2010
> URL: https://issues.jboss.org/browse/ARQ-2010
> Project: Arquillian
> Issue Type: Enhancement
> Components: Test Protocol SPIs and Implementation
> Affects Versions: 1.1.10.Final
> Reporter: Aslak Knutsen
> Assignee: Aslak Knutsen
> Fix For: 1.1.11.Final
>
>
> In particular when testing with the Arquillian Persistence extension it can be very difficult to diagnose problems in a test:
> Usually when seeding of the database fails some other After event listener fails as well, e.g. evaluation of @ShouldMatchDataSet.
> Then Arquillian only reports the last error that the actual result differs from the expected one.
> This makes fixing the test very hard.
> This PR changes the JUnitTestRunner so that it keeps the first exception that passes by ExpectedExceptionHolder.testFailure() instead of the last one.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (ARQ-2010) Report first Exception caught in TestRunner
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/ARQ-2010?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen updated ARQ-2010:
-------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/arquillian/arquillian-core/pull/97
> Report first Exception caught in TestRunner
> -------------------------------------------
>
> Key: ARQ-2010
> URL: https://issues.jboss.org/browse/ARQ-2010
> Project: Arquillian
> Issue Type: Enhancement
> Components: Test Protocol SPIs and Implementation
> Affects Versions: 1.1.10.Final
> Reporter: Aslak Knutsen
> Assignee: Aslak Knutsen
> Fix For: 1.1.11.Final
>
>
> In particular when testing with the Arquillian Persistence extension it can be very difficult to diagnose problems in a test:
> Usually when seeding of the database fails some other After event listener fails as well, e.g. evaluation of @ShouldMatchDataSet.
> Then Arquillian only reports the last error that the actual result differs from the expected one.
> This makes fixing the test very hard.
> This PR changes the JUnitTestRunner so that it keeps the first exception that passes by ExpectedExceptionHolder.testFailure() instead of the last one.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (ARQ-2010) Report first Exception caught in TestRunner
by Aslak Knutsen (JIRA)
Aslak Knutsen created ARQ-2010:
----------------------------------
Summary: Report first Exception caught in TestRunner
Key: ARQ-2010
URL: https://issues.jboss.org/browse/ARQ-2010
Project: Arquillian
Issue Type: Enhancement
Components: Test Protocol SPIs and Implementation
Affects Versions: 1.1.10.Final
Reporter: Aslak Knutsen
Assignee: Aslak Knutsen
Fix For: 1.1.11.Final
In particular when testing with the Arquillian Persistence extension it can be very difficult to diagnose problems in a test:
Usually when seeding of the database fails some other After event listener fails as well, e.g. evaluation of @ShouldMatchDataSet.
Then Arquillian only reports the last error that the actual result differs from the expected one.
This makes fixing the test very hard.
This PR changes the JUnitTestRunner so that it keeps the first exception that passes by ExpectedExceptionHolder.testFailure() instead of the last one.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months