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

Posted to dev@ignite.apache.org by "Andrew Mashenkov (JIRA)" <ji...@apache.org> on 2018/11/27 09:15:00 UTC

[jira] [Created] (IGNITE-10416) Revisit GridCacheAbstractTest childs.

Andrew Mashenkov created IGNITE-10416:
-----------------------------------------

             Summary: Revisit GridCacheAbstractTest childs.
                 Key: IGNITE-10416
                 URL: https://issues.apache.org/jira/browse/IGNITE-10416
             Project: Ignite
          Issue Type: Bug
          Components: general
            Reporter: Andrew Mashenkov


We have a lot of test inherited from GridCacheAbstractSelfTest, that code is complicated and a bit outdated regarding to the fact JUnit 4/5 is coming. 
Moreover,  starting grid from class constructor made test muting tricky and disabling cacheStore (which is always enabled by default) doesn't looks straightforward in child classes.

 

We should revisit all its childs and check if such parentness is correct.

 

First candidates are:
 # Test has own "start grid routine", but implements gridCount() method just as a dummy.
 # Before/After methods do not call parent methods. This should be handled carefully.
 # Test that doesn't expect a feature to be used, but enabled in GridCacheAbstractSelfTest.
E.g. usually, rebalance test doesn't expect cacheStore to be enabled.



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