You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Oleg Ignatenko (JIRA)" <ji...@apache.org> on 2019/01/16 07:05:00 UTC

[jira] [Updated] (IGNITE-10208) Verify list of tests after migration to Junit 4 against some prior reference (follow-up to IGNITE-10177)

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

Oleg Ignatenko updated IGNITE-10208:
------------------------------------
    Issue Type: Task  (was: Sub-task)
        Parent:     (was: IGNITE-10173)

> Verify list of tests after migration to Junit 4 against some prior reference  (follow-up to IGNITE-10177)
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-10208
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10208
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Oleg Ignatenko
>            Priority: Major
>              Labels: MakeTeamcityGreenAgain
>
> Migration from Junit 3 to 4 involves manually adding {{@Test}} annotation to existing test cases. Since Ignite contains many thousands test cases there is a substantial risk that we may miss some of these in such a transition.
> In order to mitigate the risk, suggest to do a check after completion of IGNITE-10177 and IGNITE-10762 - somehow generate list of tests in the project and compare it against similar list of tests of some "known good" prior project version (at this point, 2.7 release branch looks like a good candidate for such a reference).
> If comparison shows that some test cases from older version are missed in newer one, open a ticket to investigate that.
> Comparison is better done using [nightly run-all|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8] test set as it is the most comprehensive.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)