[jira] [Commented] (IGNITE-673) Enable broken tests with TODOs and mute them on TC

["Yakov Zhdanov (JIRA)" <ji...@apache.org>]

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

Yakov Zhdanov commented on IGNITE-673:
--------------------------------------

# TODO format is incorrec - {{// TODO it may be wrong value. Need to investigate after IGNITE-590 will be fixed.}}. proper - {{// TODO: IGNITE-590 it may be wrong value. Need to investigate after IGNITE-590 will be fixed.}}
# I would not remove todos and put {{    // Test fails: https://issues.apache.org/jira/browse/IGNITE-533.}}. Why not just uncomment test and leave TODO as is? Only exception - you should put IGNITE tickets instead of former ones.
# testMessagingPingPongListenActorExample is still commented. if we dont have this example any more, remove the test
#  {{// TODO: check for equality when IGNITE-584 fixed.}} should be                        {{ // TODO: IGNITE-584 check for equality when IGNITE-584 fixed.}}
# _testNoPrimitives() - still commented. why?
# _testComplexKeys - still commented.

Otherwise, looks good. Make sure you mute all tests you know are currently failing.



> Enable broken tests with TODOs and mute them on TC
> --------------------------------------------------
>
>                 Key: IGNITE-673
>                 URL: https://issues.apache.org/jira/browse/IGNITE-673
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Artem Shutak
>            Assignee: Yakov Zhdanov
>             Fix For: sprint-3
>
>         Attachments: ignite-sprint-3_ignite-673.patch
>
>
> Complete with TestSuites.
> branches:
> - ignite-tests-todo (part 1)
> - test-todo-2 (start working on TestSuites)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)