[
https://issues.apache.org/jira/browse/IGNITE-29026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Werner updated IGNITE-29026:
-----------------------------------
Description:
*Problem*
The compatibility test framework (IgniteContainer, IgniteClusterContainer,
IgniteRebalanceOnUpgradeTest) is rigidly hardcoded: path constants are private
static, methods are private, and container settings/configs are baked in. As a
result, tests cannot be easily reused or configured for different Ignite
images, layouts, or setups without editing the base framework code.
*Goal*
Make the framework flexible and easy to customize by introducing a minimal set
of overridable protected extension points, so test scenarios can be tuned from
subclasses without modifying the base code.
> Introduce extension points in compatibility testcontainers
> ----------------------------------------------------------
>
> Key: IGNITE-29026
> URL: https://issues.apache.org/jira/browse/IGNITE-29026
> Project: Ignite
> Issue Type: Sub-task
> Reporter: Dmitry Werner
> Assignee: Dmitry Werner
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> *Problem*
> The compatibility test framework (IgniteContainer, IgniteClusterContainer,
> IgniteRebalanceOnUpgradeTest) is rigidly hardcoded: path constants are
> private static, methods are private, and container settings/configs are baked
> in. As a result, tests cannot be easily reused or configured for different
> Ignite images, layouts, or setups without editing the base framework code.
> *Goal*
> Make the framework flexible and easy to customize by introducing a minimal
> set of overridable protected extension points, so test scenarios can be tuned
> from subclasses without modifying the base code.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
