[arquillian-issues] [JBoss JIRA] (ARQ-2026) Client activity failures should have more priority over server activities

[Christian Schulz (JIRA)]

     [ https://issues.jboss.org/browse/ARQ-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian Schulz updated ARQ-2026:
----------------------------------
              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/arquillian/arquillian-extension-warp/pull/35


> Client activity failures should have more priority over server activities
> -------------------------------------------------------------------------
>
>                 Key: ARQ-2026
>                 URL: https://issues.jboss.org/browse/ARQ-2026
>             Project: Arquillian
>          Issue Type: Enhancement
>          Components: Extension - Warp
>    Affects Versions: warp_1.0.0.Alpha7
>            Reporter: Christian Schulz
>
> I have noticed multiple times that my warp tests are failing caused by ServerWarpExecutionException.
> In my research I found out that the DefaultWarpExecutor prefers to show server activity failures over client activity failures.
> In my opinion client failures should be handled with higher priority, because in most cases the failing client activities is the reason for the server activity failure f.e. with asserts.
> I would suggest to ignore AssertionErrors from server activities if there is a catched client exception.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)