[arquillian-issues] [JBoss JIRA] (ARQ-1804) When using @Test expected exception, the internal state of the TestResult is unknown - TestNG

[Juraj Húska (JIRA)]

    [ https://issues.jboss.org/browse/ARQ-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978999#comment-12978999 ] 

Juraj Húska commented on ARQ-1804:
----------------------------------

I have verified it with current {{1.1.5.Final-SNAPSHOT}} Arquillian core, and it works for me.

Now, the reporter extension is not reporting an expected exception.

I have tested it in [this project, on this branch|https://github.com/richfaces/richfaces-qa/tree/drone2Trying/showcase-ftest].
To run the test issue:
{code}
mvn clean verify -Pwildfly-managed-8-1 -Dtest=TestAjax
{code}

> When using @Test expected exception, the internal state of the TestResult is unknown - TestNG
> ---------------------------------------------------------------------------------------------
>
>                 Key: ARQ-1804
>                 URL: https://issues.jboss.org/browse/ARQ-1804
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Test Harness Integration
>            Reporter: Aslak Knutsen
>            Priority: Minor
>             Fix For: 1.1.5.Final
>
>
> When using the ExpectedException feature in the TestFrameworks the internal TestResult object in Arquillian is in an unknown state. Arquillian catches the thrown exception, but the actual validation of it is done in the test framework after Arquillian is done with the test invocation. Arquillian can only know that a Exception has been thrown, but not if it is expected or not.
> TestNG
> @Test(expectedException=Exception.class)
> @ExpectedException(Exception.class) 
> Follow up with TestNG to see how this can be done..



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)