[OAK-3862] Move integration tests in a different Maven module

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.3.15, 1.4
• Labels: modularization technical_debt
• Epic Link: Move the Segment Store into its own bundle
• Assignee: Francesco Mari
• Reporter: Francesco Mari
• Created: 11/Jan/16 17:08
• Updated: 02/Mar/16 15:22
• Resolved: 21/Jan/16 18:25

Description

While moving the Segment Store and related packages into its own bundle, I figured out that integration tests contained in oak-core contribute to a cyclic dependency between the (new) oak-segment bundle and oak-core.

The dependency is due to the usage of NodeStoreFixture to instantiate different implementations of NodeStore in a semi-transparent way.

Tests depending on NodeStoreFixture are most likely integration tests. A clean solution to this problem would be to move those integration tests into a new Maven module, referencing the API and implementation modules as needed.

Issue Links

• blocks: OAK-3537 Move the Segment Store to its own bundle
• blocks: OAK-3905 configurable atomic counter task timeout