[jira] [Comment Edited] (IGNITE-12596) Parametrization of IgniteCacheAbstractExecutionContextTest

2020-01-29 Thread Vladimir Steshin (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-12596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17025956#comment-17025956
 ] 

Vladimir Steshin edited comment on IGNITE-12596 at 1/29/20 3:16 PM:


I think this test isn't applicable for parametrization.

1) Found different usages of set of sublclasses in test suits:

[ IgniteCacheAtomicExecutionContextTest, 
IgniteCacheReplicatedExecutionContextTest ] in IgniteCacheMvccTestSuite1

and

[ IgniteCacheAtomicExecutionContextTest, 
IgniteCacheReplicatedExecutionContextTest, IgniteCacheTxExecutionContextTest ] 
in IgniteCacheTestSuite

2) Found additional inheritances of subclasses 
IgniteCacheAtomicExecutionContextTest. That means it cannot be deleted.


was (Author: vladsz83):
I think this test isn't applicable for parametrization.

* Found different usages of set of sublclasses in test suits:

[ IgniteCacheAtomicExecutionContextTest, 
IgniteCacheReplicatedExecutionContextTest ] in IgniteCacheMvccTestSuite1

and

[ IgniteCacheAtomicExecutionContextTest, 
IgniteCacheReplicatedExecutionContextTest, IgniteCacheTxExecutionContextTest ] 
in IgniteCacheTestSuite

* Found additional inheritances of subclasses 
IgniteCacheAtomicExecutionContextTest. That means it cannot be deleted.

> Parametrization of IgniteCacheAbstractExecutionContextTest
> --
>
> Key: IGNITE-12596
> URL: https://issues.apache.org/jira/browse/IGNITE-12596
> Project: Ignite
>  Issue Type: Sub-task
> Environment: 
> org.apache.ignite.internal.processors.cache.context.IgniteCacheAbstractExecutionContextTest
>  is activated 3 times with just various params via inheritance. The problem 
> is that the extending classes are included in the target test suits not 
> always with entire combinations of params. Sometimes only 2 extendins classes 
> are involved within tests, sometimes 3. I think of using subclasses of 
> IgniteCacheAbstractExecutionContextTest as set of params.
>Reporter: Vladimir Steshin
>Assignee: Vladimir Steshin
>Priority: Minor
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Comment Edited] (IGNITE-12596) Parametrization of IgniteCacheAbstractExecutionContextTest

2020-01-29 Thread Vladimir Steshin (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-12596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17025956#comment-17025956
 ] 

Vladimir Steshin edited comment on IGNITE-12596 at 1/29/20 3:16 PM:


I think this test isn't applicable for parametrization.

* Found different usages of set of sublclasses in test suits:

[ IgniteCacheAtomicExecutionContextTest, 
IgniteCacheReplicatedExecutionContextTest ] in IgniteCacheMvccTestSuite1

and

[ IgniteCacheAtomicExecutionContextTest, 
IgniteCacheReplicatedExecutionContextTest, IgniteCacheTxExecutionContextTest ] 
in IgniteCacheTestSuite

* Found additional inheritances of subclasses 
IgniteCacheAtomicExecutionContextTest. That means it cannot be deleted.


was (Author: vladsz83):
I think this test isn't applicable for parametrization.

# Found different usages of set of sublclasses in test suits:

[ IgniteCacheAtomicExecutionContextTest, 
IgniteCacheReplicatedExecutionContextTest ] in IgniteCacheMvccTestSuite1

and

[ IgniteCacheAtomicExecutionContextTest, 
IgniteCacheReplicatedExecutionContextTest, IgniteCacheTxExecutionContextTest ] 
in IgniteCacheTestSuite

# Found additional inheritances of subclasses 
IgniteCacheAtomicExecutionContextTest. That means it cannot be deleted.

> Parametrization of IgniteCacheAbstractExecutionContextTest
> --
>
> Key: IGNITE-12596
> URL: https://issues.apache.org/jira/browse/IGNITE-12596
> Project: Ignite
>  Issue Type: Sub-task
> Environment: 
> org.apache.ignite.internal.processors.cache.context.IgniteCacheAbstractExecutionContextTest
>  is activated 3 times with just various params via inheritance. The problem 
> is that the extending classes are included in the target test suits not 
> always with entire combinations of params. Sometimes only 2 extendins classes 
> are involved within tests, sometimes 3. I think of using subclasses of 
> IgniteCacheAbstractExecutionContextTest as set of params.
>Reporter: Vladimir Steshin
>Assignee: Vladimir Steshin
>Priority: Minor
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Comment Edited] (IGNITE-12596) Parametrization of IgniteCacheAbstractExecutionContextTest

2020-01-29 Thread Vladimir Steshin (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-12596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17025956#comment-17025956
 ] 

Vladimir Steshin edited comment on IGNITE-12596 at 1/29/20 3:15 PM:


I think this test isn't applicable for parametrization.

# Found different usages of set of sublclasses in test suits:

[ IgniteCacheAtomicExecutionContextTest, 
IgniteCacheReplicatedExecutionContextTest ] in IgniteCacheMvccTestSuite1

and

[ IgniteCacheAtomicExecutionContextTest, 
IgniteCacheReplicatedExecutionContextTest, IgniteCacheTxExecutionContextTest ] 
in IgniteCacheTestSuite

# Found additional inheritances of subclasses 
IgniteCacheAtomicExecutionContextTest. That means it cannot be deleted.


was (Author: vladsz83):
I think this test isn't applicable for parametrization.

* Found different usages of set of sublclasses in test suits:

[ IgniteCacheAtomicExecutionContextTest, 
IgniteCacheReplicatedExecutionContextTest ] in IgniteCacheMvccTestSuite1

and

[ IgniteCacheAtomicExecutionContextTest, 
IgniteCacheReplicatedExecutionContextTest, IgniteCacheTxExecutionContextTest ] 
in IgniteCacheTestSuite

# Found additional inheritances of subclasses 
IgniteCacheAtomicExecutionContextTest. That means it cannot be deleted.

> Parametrization of IgniteCacheAbstractExecutionContextTest
> --
>
> Key: IGNITE-12596
> URL: https://issues.apache.org/jira/browse/IGNITE-12596
> Project: Ignite
>  Issue Type: Sub-task
> Environment: 
> org.apache.ignite.internal.processors.cache.context.IgniteCacheAbstractExecutionContextTest
>  is activated 3 times with just various params via inheritance. The problem 
> is that the extending classes are included in the target test suits not 
> always with entire combinations of params. Sometimes only 2 extendins classes 
> are involved within tests, sometimes 3. I think of using subclasses of 
> IgniteCacheAbstractExecutionContextTest as set of params.
>Reporter: Vladimir Steshin
>Assignee: Vladimir Steshin
>Priority: Minor
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)