[arquillian-issues] [JBoss JIRA] (ARQ-1012) org.junit.Assume API not working
Marc Wirth (JIRA)
jira-events at lists.jboss.org
Mon May 27 06:05:06 EDT 2013
[ https://issues.jboss.org/browse/ARQ-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12777110#comment-12777110 ]
Marc Wirth commented on ARQ-1012:
---------------------------------
Long time, but we ran into a similar issue last week. It looked like an Assume.assumeTrue(false) cause the test to fail. Digging a bit into the source code I think the problem is that the Arquillian runner (from v1.0.3) overwrites {{public void run(final RunNotifier notifier)}} but doesn't handle AssumptionViolatedException in a special way while JUnit's ParentRunner (v4.8.1) catches that and just ignores the tests:
{code}
try {
Statement statement= classBlock(notifier);
statement.evaluate();
} catch (AssumptionViolatedException e) {
testNotifier.fireTestIgnored();
}
{code}
> org.junit.Assume API not working
> --------------------------------
>
> Key: ARQ-1012
> URL: https://issues.jboss.org/browse/ARQ-1012
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Integration Test Suite
> Affects Versions: 1.0.0.Final
> Environment: Windows 7, Java 1.7
> Reporter: Karsten Ohme
>
> Hi,
> my test classes are annotated with @RunWith(Arquillian.class)
> I try to use the newer JUnit org.junit.Assume API.
> The problem ist, that the outcome of the test seems to be ignored, e.g. org.junit.Assume.assertNonNull does not fail and throws an exception.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the arquillian-issues
mailing list