You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/06/02 07:01:59 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=15311844#comment-15311844 ]
ASF GitHub Bot commented on IGNITE-3040:
----------------------------------------
Github user vldpyatkov closed the pull request at:
https://github.com/apache/ignite/pull/667
> 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
> Fix For: 1.7
>
>
> 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)