You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Goncharuk (Jira)" <ji...@apache.org> on 2019/09/12 13:55:00 UTC
[jira] [Commented] (IGNITE-11708) Unable to run tests in
IgniteConfigVariationsAbstractTest subclasses
[ https://issues.apache.org/jira/browse/IGNITE-11708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16928552#comment-16928552 ]
Alexey Goncharuk commented on IGNITE-11708:
-------------------------------------------
[~ivanan.fed] [~Pavlukhin] please set fix versions when resolving tickets.
> Unable to run tests in IgniteConfigVariationsAbstractTest subclasses
> --------------------------------------------------------------------
>
> Key: IGNITE-11708
> URL: https://issues.apache.org/jira/browse/IGNITE-11708
> Project: Ignite
> Issue Type: Bug
> Reporter: Ivan Fedotov
> Assignee: Ivan Fedotov
> Priority: Major
> Labels: iep-30
> Attachments: read_through_eviction_self_test.patch, tx_out_test_fixed.patch
>
> Time Spent: 4h
> Remaining Estimate: 0h
>
> It seems that test classes that extend from IgniteConfigVariationsAbstractTest cannot be started with JUnit4 @Test annotation.
> It is easy to check: if throw exception in any test methods, nothing will happen.
> Reason can be in rule chain in IgniteConfigVariationsAbstractTest class [1], maybe it destroys existing test workflow.
> [1] https://github.com/apache/ignite/blob/master/modules/core/src/test/java/org/apache/ignite/testframework/junits/IgniteConfigVariationsAbstractTest.java#L62
--
This message was sent by Atlassian Jira
(v8.3.2#803003)