[
https://issues.apache.org/jira/browse/IGNITE-11708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16847363#comment-16847363
]
Ivan Pavlukhin commented on IGNITE-11708:
-----------------------------------------
[~ivanan.fed] I see a problem in
{{IgniteCacheConfigVariationsAbstractTest#beforeTestsStarted}} by design it
prestarts a cluster. And to do it properly it requires _testsCfg_ (instance
variable) to be already initialized. And it seems that with a previous rules
stacking approach it worked. I do not have good ideas in my mind so far. Will
think about it. Currently a couple of raw ideas:
* Consider using static variable instead _testsCfg_.
* Do not initialize _testsCfg_ with a default value to avoid skipping a real
config which is expected to be injected.
> 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: iep30
> Attachments: read_through_eviction_self_test.patch,
> tx_out_test_fixed.patch
>
> Time Spent: 3h 20m
> 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
(v7.6.3#76005)
