Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAPJKmXm7=LQvL2e8=LaP82+d862EE77q=-f-yktbxhaBuBD_QA@mail.gmail.com>
References: 
 <CAPJKmXkdAsZQGpVr_Zb8SmKEu4YMBpE1XDuS2b3z0E6g1FZyZA@mail.gmail.com>
 <CA+0=VoW8-EsxNRdFVwwcfvbjfAWnDPuNiu-6th-ctds3P6mAQQ@mail.gmail.com>
 <CAPJKmXm2_2=YJNhBE=+-7AjvXRTOPcdEhCMH_knz9C29FNs=Fg@mail.gmail.com>
 <CAPJKmXm_bcxt-huV3PQT8SiqLYS9h4VM_aBw+vbk_M6g_uPdEw@mail.gmail.com>
 <CA+0=VoUzoNAaEQipvgOJnxaXD1qDR1Mg18joNnwV2deUo2whuA@mail.gmail.com>
 <CAPJKmXm7=LQvL2e8=LaP82+d862EE77q=-f-yktbxhaBuBD_QA@mail.gmail.com>
From: Dmitriy Setrakyan <dsetrakyan@apache.org>
Date: Wed, 3 Feb 2016 08:36:48 -0800
Message-ID: 
 <CA+0=VoXfpz1tir1k2iDdG46rLGBcrF-Q8d-k4XRU7im_-pCJmw@mail.gmail.com>
Subject: Re: Full API coverage enhancement
To: dev@ignite.apache.org
Content-Type: multipart/alternative; boundary=089e0111dfcad0addf052ae03b46

--089e0111dfcad0addf052ae03b46
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Thanks Artem! In your view, how many combinations of the configuration
properties will be tested together. I don=E2=80=99t think we can afford to =
test
every possible combination.

On Wed, Feb 3, 2016 at 7:40 AM, Artem Shutak <ashutak@gridgain.com> wrote:

> Dmitriy,
>
> Actually, I don't have a list with all the permutations.
>
> At first, we need to split in our discussion test cases and Ignite
> configuration which should be covered.
>
> For example, new Full Api test cases for cache are based on old Full Api
> test cases. So, it need to think what the test cases was not covered
> before.
>
> About Ignite configurations, I'm going to add permutation for each
> IgniteConfiguration and CacheConfiguration property.
>
> By the way, the jira contains the following list of permutation (feel fre=
e
> to add something):
>
> The following tests should be added (for functional blocks):
>
>    1. Interceptor
>    2. Queries: continuous, scan, SQL, fields and text queries.
>    3. cache events
>    4. We should also test with Serializable, Externalizable, and plain
>    Pojos for keys and values.
>    5. The Pojo in the above test should contain an enum value
>    6. We should also test Enums as keys and Enums as values
>    7. All operations should have single-key and multi-key operations
>
> New tests should cover all combinations for following properties:
>
>    1. cache modes
>    2. operation from client nodes and server nodes
>    3. store enabled/disabled
>    4. evicts sycn/non-sync
>    5. eviction policies
>    6. near on/off
>    7. marshallers (+ Binary marshaller with different mappers)
>    8. keys and values - externalizable, serializable, binaryzable, "none =
of
>    previous"
>    9. classes available on servers: true/false
>    10. Peer loading on/off
>    11. Affinity functions
>    12. expiry policies
>
>
> Thanks,
> -- Artem --
>
> On Wed, Feb 3, 2016 at 6:14 PM, Dmitriy Setrakyan <dsetrakyan@apache.org>
> wrote:
>
> > Artem, I think it is best to specify all the permutations here, so othe=
rs
> > can make additional suggestions. Otherwise, we cannot get a full pictur=
e.
> >
> > Thanks,
> > D.
> >
> > On Wed, Feb 3, 2016 at 2:02 AM, Artem Shutak <ashutak@gridgain.com>
> wrote:
> >
> > > Igniters,
> > >
> > > I thought a little bit more and think we need to add a support for th=
e
> > > following permutations too (I've added these to the jira description)=
:
> > > - 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
> > >
> > > Maybe someone see any other permutation to be supported?
> > >
> > > -- Artem --
> > >
> > > On Tue, Feb 2, 2016 at 10:05 PM, Artem Shutak <ashutak@gridgain.com>
> > > wrote:
> > >
> > > > Dmitriy,
> > > >
> > > > There is a branch at my fork and a pull request at Ignite. See
> comment
> > > > about pull request at the ticket (PR-446).
> > > >
> > > > But I have to notice that the branch under hard development and you
> it
> > > can
> > > > not work (have compilation or test errors) at some moments.
> > > >
> > > > Good luck!
> > > >
> > > > -- Artem --
> > > >
> > > > On Tue, Feb 2, 2016 at 9:45 PM, Dmitriy Setrakyan <
> > dsetrakyan@apache.org
> > > >
> > > > wrote:
> > > >
> > > >> Artem,
> > > >>
> > > >> This is great. I have noticed from the ticket that you have create=
d
> > some
> > > >> initial suite already. Is there a branch I can look at it?
> > > >>
> > > >> D.
> > > >>
> > > >> On Tue, Feb 2, 2016 at 10:02 AM, Artem Shutak <ashutak@gridgain.co=
m
> >
> > > >> wrote:
> > > >>
> > > >> > Igniters,
> > > >> >
> > > >> > I'm working on an enhancement of Full API coverage [1] [2].
> > > >> >
> > > >> > Ignite already has Full API test, but currently it's hard to tes=
t
> > all
> > > >> > configuration combinations.
> > > >> >
> > > >> > Feel free to add comments in the jira if you have any thought.
> > > >> >
> > > >> > [1] https://issues.apache.org/jira/browse/IGNITE-2521
> > > >> > [2]
> > > >>
> https://cwiki.apache.org/confluence/display/IGNITE/Implementing+Tests
> > > >> >
> > > >> > Thanks,
> > > >> > -- Artem --
> > > >> >
> > > >>
> > > >
> > > >
> > >
> >
>

--089e0111dfcad0addf052ae03b46--