Excerpt |
---|
This page descibes hits for developing and researching failures of Apache Ignite tests |
Table of Contents |
---|
Ignite test has build in Framework to test compatibilty. This framework provides an opportunity to start working with Ignite instances of previously released versions.
...
It’s very easy to use it for writing unit tests, here is a simple example which demonstrates the main functional.
This test checks that everything that is on the public API in the configuration, is there in the .NET, unless specified otherwise. Exceptions are:
If there is a public API, but it is not in the .NET class, or in the list of unnecessary, or in the list of known unsupported, then the test fails. This fix explicitly marks the property as yet unimplemented in class
modules/platforms/dotnet/Apache.Ignite.Core.Tests/ApiParity/IgniteConfigurationParityTest.cs
there is String array MissingProperties. This array stores properties that are missing on .NET side. Adding property to this list disable Parity test fails, but it is reasonable to add properties only with corresponding issue creation first. Issue number can be added as comment