[jira] [Resolved] (SLING-13064) [Sling Models] Migrate 'via' package unit tests to JUnit 5

["Stefan Seifert (Jira)" <ji...@apache.org>]

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

Stefan Seifert resolved SLING-13064.
------------------------------------
    Fix Version/s: Models Implementation 2.0.2
         Assignee: Stefan Seifert
       Resolution: Fixed

https://github.com/apache/sling-org-apache-sling-models-impl/commit/ce484b73631bf5fba5c7ab55d59aef11b8b217fd

thanks for the contribution!

> [Sling Models] Migrate 'via' package unit tests to JUnit 5
> ----------------------------------------------------------
>
>                 Key: SLING-13064
>                 URL: https://issues.apache.org/jira/browse/SLING-13064
>             Project: Sling
>          Issue Type: Improvement
>            Reporter: Bhavik Kothari
>            Assignee: Stefan Seifert
>            Priority: Major
>             Fix For: Models Implementation 2.0.2
>
>
> Continuing the JUnit 5 migration efforts (following SLING-13052, SLING-13062 and SLING-13063).
> This task migrates the unit tests in the `org.apache.sling.models.impl.via` package to JUnit 5.
> These tests cover various "Via" providers and ResourceTypeForcing wrappers,
> *  AbstractResourceTypeViaProviderTest
> * BeanPropertyViaProviderTest
> * ChildResourceViaProviderTest
> * ForcedResourceTypeViaProviderTest
> * OriginalResourceTypeViaProviderTest
> * ResourceSuperTypeViaProviderTest
> * ResourceTypeForcingJakartaRequestWrapperTest
> * ResourceTypeForcingRequestWrapperTest
> Changes:
>  - Replacing `MockitoJUnitRunner` with `@ExtendWith(MockitoExtension.class)`.
>  - Updating all imports to `org.junit.jupiter.api`.
>  - Applying `lenient()` strictness to shared setup method to preserve legacy test behavior and prevent `UnnecessaryStubbingException` without altering the original test logic



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