You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ivan Fedotov (JIRA)" <ji...@apache.org> on 2019/08/09 13:06:00 UTC

[jira] [Comment Edited] (IGNITE-10973) Migrate example module tests from Junit 4 to 5

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

Ivan Fedotov edited comment on IGNITE-10973 at 8/9/19 1:05 PM:
---------------------------------------------------------------

[~Pavlukhin], Seems that the .net problem is the last one.

I brought the full context of the problem in the conversation. The problem is more general, JUnit migration looks like a consequence, not a cause.

[1] http://apache-ignite-developers.2346864.n4.nabble.com/Test-naming-on-TC-JUnit-5-tp42750p42810.html



was (Author: ivanan.fed):
Seems that the .net problem is the last one.

I brought the full context of the problem in the conversation. The problem is more general, JUnit migration looks like a consequence, not a cause.

[1] http://apache-ignite-developers.2346864.n4.nabble.com/Test-naming-on-TC-JUnit-5-tp42750p42810.html


> Migrate example module tests from Junit 4 to 5
> ----------------------------------------------
>
>                 Key: IGNITE-10973
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10973
>             Project: Ignite
>          Issue Type: Sub-task
>            Reporter: Ivan Fedotov
>            Assignee: Ivan Fedotov
>            Priority: Major
>              Labels: iep-30
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> For more information refer parent task.
> Migrate from Junit 4 to 5 in the example module.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)