You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexei Scherbakov (JIRA)" <ji...@apache.org> on 2016/04/25 18:50:13 UTC
[jira] [Commented] (IGNITE-3041) Implement config variations test
for IgniteServices
[ https://issues.apache.org/jira/browse/IGNITE-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15256578#comment-15256578 ]
Alexei Scherbakov commented on IGNITE-3041:
-------------------------------------------
Added coverage for all methods from IgniteServices.
Submitted to TC.
> Implement config variations test for IgniteServices
> ---------------------------------------------------
>
> Key: IGNITE-3041
> URL: https://issues.apache.org/jira/browse/IGNITE-3041
> Project: Ignite
> Issue Type: Test
> Components: managed services
> Reporter: Semen Boikov
> Assignee: Alexei Scherbakov
> Fix For: 1.6
>
>
> Need implement configuration variations test for IgniteServices (use IgniteComputeConfigVariationsFullApiTest developed in IGNITE-3019 as example).
> Test should cover following cases:
> - all supported marshaller (Optimized, Binary, JDK)
> - single server
> - multiple servers, multiple clients: service is deployed from server/client, service is called from server/client
> - Serializable, Externalizable, Binarylizable service (see IgniteConfigVariationsAbstractTest.runInAllDataModes)
> - call service method with plain, Serializable, Externalizable, Binarylizable argument/return value (i.e. with all data types from IgniteConfigVariationsAbstractTest.runInAllDataModes)
> - true/false for IgniteConfiguration.peerClassLoadingEnabled
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)