ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Artem Shutak (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-2521) Need to increase test coverage (support all configurations combinations)
Date Thu, 25 Feb 2016 14:59:18 GMT

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

Artem Shutak commented on IGNITE-2521:

Finished with the permutation configuration framework and POC based on Cache Full API tests.

How to use the configurations permutations test framework:
- Test class has to extend {{IgniteConfigPermutationsAbstractTest}} or {{IgniteCacheConfigPermutationsAbstractTest}}.
- TestSuite has to be built using {{ConfigPermutationsTestSuiteBuilder}}.

How framework works internally.
- All Ignite cluster will be started for each {{IgniteConfiguration}} and will be stopped
before testing next {{IgniteConfiguration}}.
- In case of {{IgniteCacheConfigPermutationsAbstractTest}}, caches will be started and stopped
dynamically for each {{CacheConfiguration}} (only once).

> 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
> # 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

View raw message