[
https://issues.apache.org/jira/browse/IGNITE-11708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16814558#comment-16814558
]
Ivan Pavlukhin commented on IGNITE-11708:
-----------------------------------------
[~ivanan.fed], the problem seems to be a mistake in
{code}
private final TestRule rulePrivate = (base, description) -> new Statement() {
@Override public void evaluate() {
assert getName() != null : "getName returned null";
testsCfg = testsCfgInjected;
}
};
{code}
It simply does not call {{base.evaluate}} inside.
But also I suggest to address following items as well:
# Fix rules execution order for {{IgniteConfigVariationsAbstractTest}}.
# Unignore ignored tests.
# Add code making sure that _variation_ tests are really executed but not
skipped.
# Pay attention to other _variation_ tests. I saw that {{LegacyLifecycleTest}}
used {{@BeforeClass}} annotation but an annotated methods was not executed.
> 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
> Time Spent: 10m
> 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)
