You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Ivan Pavlukhin (JIRA)" <ji...@apache.org> on 2019/02/25 18:59:00 UTC

[jira] [Issue Comment Deleted] (IGNITE-11356) Test framework: Remove custom assumption exceptions handling

     [ https://issues.apache.org/jira/browse/IGNITE-11356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ivan Pavlukhin updated IGNITE-11356:
------------------------------------
    Comment: was deleted

(was: Apparently, some glitches are possible after explicit lock removal. So, I reverted PR to an initial stage. First visa corresponds to that state.)

> Test framework: Remove custom assumption exceptions handling
> ------------------------------------------------------------
>
>                 Key: IGNITE-11356
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11356
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Ivan Pavlukhin
>            Assignee: Ivan Pavlukhin
>            Priority: Major
>              Labels: MakeTeamcityGreenAgain
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> It turns out that custom handling of {{AssumptionViolatedException}} can be removed. Currently with custom handling tests with unmet assumptions are marked as passed. With default handling failed assumptions on instance level mark tests as ignored.
> Note: on class level reporting in case of unmet assumptions does not look perfect. But with custom handling a particular test is not included into TC report at all.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)