Let imagine class like:

@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 { ... }
}

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?