[
https://issues.apache.org/jira/browse/IGNITE-11413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16807641#comment-16807641
]
Ivan Fedotov commented on IGNITE-11413:
---------------------------------------
[~Pavlukhin],
In principal {{beforeTest/afterTest}} methods now work from rule. It is clear
from {{GridAbstractTest}} class: methods are used in {{setUp}}, {{tearDown}}
respectively. And the last ones are used under rule in {{runTest}} method [1].
What kind of work do you mean?
[1][https://github.com/apache/ignite/blob/master/modules/core/src/test/java/org/apache/ignite/testframework/junits/GridAbstractTest.java#L2035]
> Remove beforeTestsStarted, afterTestsStarted from JUnit3TestLegacySupport
> -------------------------------------------------------------------------
>
> Key: IGNITE-11413
> URL: https://issues.apache.org/jira/browse/IGNITE-11413
> Project: Ignite
> Issue Type: Improvement
> Reporter: Ivan Fedotov
> Assignee: Ivan Fedotov
> Priority: Major
> Labels: iep-30
>
> beforeTestsStarted and afterTestsStarted methods are deprecated in context of
> JUnit4 functional. The 4th version provides @BeforeClass, @AfterClass
> annotations for such purposes. Methods must be moved in corresponded classes
> and marked by annotations.
> It could require changes in start/stop nodes process because methods under
> @BeforeClass, @AfterClass annotations must be static.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
