ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ignite TC Bot (Jira)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-12135) Rework GridCommandHandlerTest
Date Tue, 03 Sep 2019 14:29:00 GMT

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

Ignite TC Bot commented on IGNITE-12135:
----------------------------------------

{panel:title=Branch: [pull/6833/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--&gt; Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=4560479&amp;buildTypeId=IgniteTests24Java8_RunAll]

> Rework GridCommandHandlerTest
> -----------------------------
>
>                 Key: IGNITE-12135
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12135
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Kirill Tkalenko
>            Assignee: Kirill Tkalenko
>            Priority: Major
>             Fix For: 2.8
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> There are 50+ tests. In each test we are start and stop nodes. I think we could split
tests at least to two groups:
>  # Tests on normal behaviour. We could start nodes before all tests and stop them after
all tests.
>  # Tests required start new cluster before each test.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Mime
View raw message