[IGNITE-10416] Revisit GridCacheAbstractTest childs.

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: general
• Labels: MakeTeamcityGreenAgain
• Ignite Flags: Docs Required
• Assignee: Unassigned
• Reporter: Andrey Mashenkov
• Created: 27/Nov/18 09:14
• Updated: 27/Nov/18 09:14

Description

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:

1. Test has own "start grid routine", but implements gridCount() method just as a dummy.
2. Before/After methods do not call parent methods. This should be handled carefully.
3. 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.