[
https://issues.apache.org/jira/browse/IGNITE-28237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18066940#comment-18066940
]
Ignite TC Bot commented on IGNITE-28237:
----------------------------------------
{panel:title=Branch: [pull/12902/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 7{color} [[tests 0 TIMEOUT , Exit Code
|https://ci2.ignite.apache.org/viewLog.html?buildId=8940173]]
{panel}
{panel:title=Branch: [pull/12902/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=8938063&buildTypeId=IgniteTests24Java8_RunAll]
> Finalize Mockito 5 migration and fix incompatible tests
> -------------------------------------------------------
>
> Key: IGNITE-28237
> URL: https://issues.apache.org/jira/browse/IGNITE-28237
> Project: Ignite
> Issue Type: Sub-task
> Reporter: Kirill Anisimov
> Assignee: Kirill Anisimov
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {{mockito.version}} is already set to {{5.21.0}} in the parent POM.
> The task is to finalize Mockito 5 migration by fixing incompatible test code
> and validating test execution.
> h3. Problem:
> Several tests still used internal Mockito APIs from org.mockito.internal.*.
> This is unsafe because internal Mockito classes are implementation details
> and are not covered by compatibility guarantees across major versions.
> Keeping such usages after migration to Mockito 5 could lead to brittle tests
> and future breakages even if the current dependency version resolves
> successfully.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
