[
https://jira.jboss.org/browse/ARQ-181?page=com.atlassian.jira.plugin.syst...
]
Pete Muir updated ARQ-181:
--------------------------
Summary: When using @Test expected exception, the internal state of the TestResult is
unknown (was: When using @Text expected exception, the internal state of the TestResult
is unknown)
When using @Test expected exception, the internal state of the
TestResult is unknown
------------------------------------------------------------------------------------
Key: ARQ-181
URL:
https://jira.jboss.org/browse/ARQ-181
Project: Arquillian
Issue Type: Bug
Components: Test Harness Integration
Reporter: Aslak Knutsen
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.
JUnit
@Test(expected=Exception.class)
TestNG
@Test(expectedException=Exception.class)
@ExpectedException(Exception.class)
Follow up with TestNG and JUnit to see how this can be done..
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira