You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Roman Puchkovskiy (Jira)" <ji...@apache.org> on 2022/12/28 11:55:00 UTC

[jira] [Created] (IGNITE-18481) Add a mechanism to provide integration tests with all storage engines

Roman Puchkovskiy created IGNITE-18481:
------------------------------------------

             Summary: Add a mechanism to provide integration tests with all storage engines
                 Key: IGNITE-18481
                 URL: https://issues.apache.org/jira/browse/IGNITE-18481
             Project: Ignite
          Issue Type: Improvement
            Reporter: Roman Puchkovskiy


Currently, if we want to test something for all storage engines that we support, we hard-code the list of engines. This has a risk that, if we add a new storage engine, we forget to add it to the list of tested engines, so it remains untested.

Here are some ideas:
 # Use service loaders to find the storage engines. This has a drawback of implicitness, that is, if the mechanism fails to find an engine, we might miss that unfortunate event, and some engine might become untested.
 # Use a centrally-maintained hard-coded list of all storage engines. The drawback is that we might forget to add a new engine.
 # Combination of both. Add some automagic facilities that will find the storage engines using service loaders (and supply them to tests), but also maintain a hand-crafted list of all production storage engines, and add a test that makes sure that the 2 mechanisms yield same results. This approach allows us to use automagic, but also have explicitness of hard-coding.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)