You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Semen Boikov (JIRA)" <ji...@apache.org> on 2016/05/12 10:20:12 UTC
[jira] [Commented] (IGNITE-3040) Implement config variations test
for IgniteMessaging
[ https://issues.apache.org/jira/browse/IGNITE-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15281400#comment-15281400 ]
Semen Boikov commented on IGNITE-3040:
--------------------------------------
Reviewed, have some comments:
- please change test to use regular static CountDownLatch instead of IgniteCountDownLatch
- please fix test to really test 'client->clent' e.t.c modes. For example in test 'testClientClientMessage' method 'send' must be called from client node, now you always call send using node 'grid(SERVER_NODE_IDX)'
> Implement config variations test for IgniteMessaging
> ----------------------------------------------------
>
> Key: IGNITE-3040
> URL: https://issues.apache.org/jira/browse/IGNITE-3040
> Project: Ignite
> Issue Type: Test
> Components: messaging
> Reporter: Semen Boikov
> Assignee: Vladislav Pyatkov
> Fix For: 1.6
>
>
> Need implement configuration variations test for IgniteMessaging (use IgniteComputeConfigVariationsFullApiTest developed in IGNITE-3019 as example).
> Test should cover following cases:
> - all supported marshaller (Optimized, Binary, JDK)
> - different data types for message topics, messages (see IgniteConfigVariationsAbstractTest.runInAllDataModes)
> - single server node
> - multiple servers, multiple clients, send message from server->client, client->client, client->server
> - true/false for IgniteConfiguration.peerClassLoadingEnabled
> - all 'sendXXX' method from IgniteMessaging
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)