Hi, Igniters! I would like to announce new Compatibility Testing Framework module in the project.
This module has been recently included in the project [1]. Framework provides an opportunity to start working with Ignite instances of previously released versions. The entire module is built on top of the Ignite Testing Framework, especially on the MiltiJVM-mode classes. There is a class IgniteCompatibilityAbstractTest that provides methods to start Ignite nodes with versions which have been previously released in the Maven repository in separate JVM and allows them to join topology. Framework looking for artifacts of a specific version in the Maven local repository, if they don’t exist there, they will be downloaded and stored via Maven. The main implemented API: startGrid(name, version, configurationClosure); startGrid(name, version, configurationClosure, postStartupClosure); You can simply specify a version of Ignite, which you want to start, define the configuration in the configurationClosure and set the actions on the started node in the postStartupClosure. It’s very easy to use it for writing unit tests, here is a simple example [2] which demonstrates the main functional. I hope this framework helps us to make our project even better. I want to thank Anton Vinogradov for his help with API design and Dmitriy Pavlov for sharing first-time user experience [3] [4]. [1] https://issues.apache.org/jira/browse/IGNITE-5732 - Provide API to test compatibility with old releases [2] https://github.com/apache/ignite/blob/master/modules/compatibility/src/test/java/org/apache/ignite/compatibility/persistence/DummyPersistenceCompatibilityTest.java [3] http://apache-ignite-developers.2346864.n4.nabble.com/Binary-compatibility-of-persistent-storage-tp22419p22913.html [4] https://issues.apache.org/jira/browse/IGNITE-6285 - Enhance persistent store paths on start -- Best Regards, Vyacheslav D.
