[jira] [Commented] (IGNITE-29026) Introduce extension points in compatibility testcontainers

["Ignite TC Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-29026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18118649#comment-18118649 ] 

Ignite TC Bot commented on IGNITE-29026:
----------------------------------------

{panel:title=Branch: [pull/13540/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/13540/head] Base: [master] : No new tests found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All* Results|https://ci2.ignite.apache.org/viewLog.html?buildId=9361544&buildTypeId=IgniteTests24Java8_RunAll]
{color:#ffffff}tcbot-analysis-comment chainBuildId=9361544 rerunBuildIds=none{color}

> 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: 2h 20m
>  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)