[arquillian-issues] [JBoss JIRA] (ARQ-705) @ShouldThrowException() - if expected deployment exception is not raised it will stop to invoke other deployments and any tests aren't processed at all

[Pavel Janousek (Commented) (JIRA)]

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

Pavel Janousek commented on ARQ-705:
------------------------------------

Aslak, maybe you are right. But from my PoV the class level assertion (TestCase) in this case (real example) is web.xml configuration parameter and its processing. So my concern is around this testing - so when a parameter is boolean type - I've 3 different deployments (with true, false, invalid value). If I'll continue with your approach I need 3 classes with almost the same implementation differs only on deployment. Lets imagine - I've ten such parameters... (and some of them could have more values than 3).

But your are right, dep2 is absolutely independent to dep1.
                
> @ShouldThrowException() - if expected deployment exception is not raised it will stop to invoke other deployments and any tests aren't processed at all
> -------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ARQ-705
>                 URL: https://issues.jboss.org/browse/ARQ-705
>             Project: Arquillian
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Pavel Janousek
>
> Let imagine class like:{code}
> @RunWith(Arquillian.class)
> public class ImagineTestCase {
>   @Deployment(name="dep1")
>   @ShouldThrowException(Exception.class)
>   public static Archive<?> dep1() { ... }
>   @Deployment(name="dep2")
>   public static Archive<?> dep2() { ... }
>   @Test
>   @OperateOnDeployment("dep1")
>   public void Test1() throws Exception { ... }
>   @Test
>   @OperateOnDeployment("dep2")
>   public void Test2() throws Exception { ... }
> }
> {code}
> Present behavior - if exception isn't raised during deployment dep1 (and this is also the first deployment ARQ want to run), everything other is stopped, although deployment dep2 could work ok and Test2() depends only on dep2.
> It doesn't make sense for me, I prefer to continue run some tests if anyone is available and isn't blocked by failed deployment -> try to run dep2(), deploy produced artifact and invoke Test2, even dep1() failed (not raised Exception in this case).
> Do you agree with me?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira