[jira] [Updated] (SLING-12162) Update o.a.s.junit.core to jupiter 5.10.1

["Julian Sedding (Jira)" <ji...@apache.org>]

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

Julian Sedding updated SLING-12162:
-----------------------------------
    Fix Version/s: JUnit Core 1.1.8

> Update o.a.s.junit.core to jupiter 5.10.1
> -----------------------------------------
>
>                 Key: SLING-12162
>                 URL: https://issues.apache.org/jira/browse/SLING-12162
>             Project: Sling
>          Issue Type: Task
>          Components: JUnit Core
>    Affects Versions: JUnit Core 1.1.6
>            Reporter: Julian Sedding
>            Assignee: Julian Sedding
>            Priority: Major
>             Fix For: JUnit Core 1.1.8
>
>
> In the context of [PR #20|https://github.com/apache/sling-org-apache-sling-junit-core/pull/20], it turned out that a change between jupiter 5.10.0 and 5.10.1 brakes a test case.
> I have identified the [relevant change|https://github.com/junit-team/junit5/pull/3500/files#diff-eec44cb3c2bd65dc0944562c5b919097b7995cbbd874f3ff6f9cd1dd170a2814R1506-L1510] to be stricter enforcement of a test method predicate. It turns out that we have a meta-test (we're running tests within tests for o.a.s.junit.core) that overrides and inherited test method, but does not itself add the `@Test` annotation on it. That way the test method in question is not found, which fails an assertion that checks if any meta-tests were run.
> cc [~apelluru]



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