[ 
https://issues.apache.org/jira/browse/IGNITE-28532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Maksim Davydov updated IGNITE-28532:
------------------------------------
    Description: 
This ticket proposes the addition of a dedicated JUnit-based testing framework 
to simplify and standardize rolling upgrade (RU) testing in Apache Ignite.

The framework will provide:
* A fluent, developer-friendly API for defining mixed-version cluster 
topologies and upgrade sequences.
* Automated orchestration of node lifecycle (start, stop, restart with version 
switching) across multiple JVMs.
* Built-in support for parameterized version matrices to systematically 
validate compatibility across releases.
* Reusable hooks for pre-upgrade, during-upgrade, and post-upgrade test logic.

By building on the existing `IgniteCompatibilityAbstractTest` infrastructure, 
the framework eliminates boilerplate, reduces maintenance overhead, and enables 
contributors to easily add robust upgrade tests for new features (SQL, Cache, 
Compute, etc.).

*Goal*: Improve developer productivity and test coverage for rolling upgrade 
scenarios.

> Introduce JUnit Rolling Upgrade Testing Framework
> -------------------------------------------------
>
>                 Key: IGNITE-28532
>                 URL: https://issues.apache.org/jira/browse/IGNITE-28532
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Maksim Davydov
>            Assignee: Maksim Davydov
>            Priority: Major
>              Labels: IEP-132, ise
>             Fix For: 2.19
>
>
> This ticket proposes the addition of a dedicated JUnit-based testing 
> framework to simplify and standardize rolling upgrade (RU) testing in Apache 
> Ignite.
> The framework will provide:
> * A fluent, developer-friendly API for defining mixed-version cluster 
> topologies and upgrade sequences.
> * Automated orchestration of node lifecycle (start, stop, restart with 
> version switching) across multiple JVMs.
> * Built-in support for parameterized version matrices to systematically 
> validate compatibility across releases.
> * Reusable hooks for pre-upgrade, during-upgrade, and post-upgrade test logic.
> By building on the existing `IgniteCompatibilityAbstractTest` infrastructure, 
> the framework eliminates boilerplate, reduces maintenance overhead, and 
> enables contributors to easily add robust upgrade tests for new features 
> (SQL, Cache, Compute, etc.).
> *Goal*: Improve developer productivity and test coverage for rolling upgrade 
> scenarios.



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

Reply via email to