ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Ignatenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-10208) Verify list of tests after migration to Junit 4 against some prior reference (follow-up to IGNITE-10177)
Date Fri, 09 Nov 2018 14:12:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-10208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16681487#comment-16681487
] 

Oleg Ignatenko commented on IGNITE-10208:
-----------------------------------------

[~skozlov] if you have any considerations on how this task could be done, I would appreciate.
Prior to creating it I googled a bit on how this could be done, specifically if there is a
way to generate list of test names in a maven / junit project but couldn't find anything useful.

[~dpavlov] as you are involved in TC bot you may also know something on this matter. If you
have any ideas on how this task could be done, please feel free to share.

> 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: Sub-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
- 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.



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

Mime
View raw message