[
https://issues.apache.org/jira/browse/IGNITE-2521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15152018#comment-15152018
]
Artem Shutak commented on IGNITE-2521:
--------------------------------------
I'm finishing a work on Basic set of configuration permutations.
Done:
- Added tests for put, get, getAll and invoke operations which test operations
in different data modes: Serializeable, Externalizable and Plane objects. All
tests pass for server nodes (except IGNITE-2664).
- Implemented a configuration mechanism to run the same tests in server and
different client modes (near-only / without near cache) without additional
cache restarts. Cluster has 3 server nodes and 2 client nodes (with/without
near) and all tests executed for server then for client with near cache and
then for client without near cache.
Need to fix tests for client mode without near cache.
Need to add testInvoke/testInvokeAll for cache withKeepBinary
> Need to increase test coverage (support all configurations combinations)
> ------------------------------------------------------------------------
>
> Key: IGNITE-2521
> URL: https://issues.apache.org/jira/browse/IGNITE-2521
> Project: Ignite
> Issue Type: Task
> Reporter: Artem Shutak
> Assignee: Artem Shutak
>
> The purpose of this ticket is to make sure that all cache operations should
> work for any config props combination.
> New test suite should be created. Cache full API tests should be used as
> start point.
> The following tests should be added (for functional blocks):
> # Interceptor
> # Queries: continuous, scan, SQL, fields and text queries.
> # cache events
> # We should also test with Serializable, Externalizable, and plain Pojos for
> keys and values.
> # The Pojo in the above test should contain an enum value
> # We should also test Enums as keys and Enums as values
> # All operations should have single-key and multi-key operations
> New tests should cover all combinations for following properties:
> # cache modes
> # operation from client nodes and server nodes
> # store enabled/disabled
> # evicts sycn/non-sync
> # eviction policies
> # near on/off
> # marshallers (+ Binary marshaller with different mappers)
> # keys and values - externalizable, serializable, binaryzable, "none of
> previous"
> # classes available on servers: true/false
> # Peer loading on/off
> # Affinity functions
> # expiry policies
> One more thing for new tests: I think test should start both server and
> client nodes and use Ignite API from all nodes.
> Design notes
> # New tests should accept cache/grid configuration on creation or via setter
> method
> # Enclosing suite should have a collection of all configurations prebuilt or
> should be able to generate the full set of configurations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
