[
https://issues.apache.org/jira/browse/IGNITE-20720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtcev updated IGNITE-20720:
-----------------------------------------
Description:
We have two classes that are used to write integration tests that can start an
Ignite cluster. I would propose two improvements regarding these classes:
# They are located in different packages (ClusterPerClassIntegrationTest is in
the {{sql}} package for some reason). I suggest to move these classes together
and unify their API.
# They are not part of the test API and other modules cannot access them. I
suggest to move these two classes to Test Fixtures.
was:
We have two classes that are used to write integration tests that can start an
Ignite cluster. I would propose two improvements regarding these classes:
# They are located in different packages (
> Move ClusterPerTestIntegrationTest and ClusterPerClassIntegrationTest to Test
> Fixtures
> --------------------------------------------------------------------------------------
>
> Key: IGNITE-20720
> URL: https://issues.apache.org/jira/browse/IGNITE-20720
> Project: Ignite
> Issue Type: Improvement
> Reporter: Aleksandr Polovtcev
> Assignee: Aleksandr Polovtcev
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> We have two classes that are used to write integration tests that can start
> an Ignite cluster. I would propose two improvements regarding these classes:
> # They are located in different packages (ClusterPerClassIntegrationTest is
> in the {{sql}} package for some reason). I suggest to move these classes
> together and unify their API.
> # They are not part of the test API and other modules cannot access them. I
> suggest to move these two classes to Test Fixtures.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
