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-648) Implement framework for multi JVM unit tests
Date Thu, 23 Jul 2015 09:52:04 GMT

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

Artem Shutak commented on IGNITE-648:
-------------------------------------

Results.

We can run grid instances in unit tests in separate jvms just switching isMultyJvm to true.

A proof of concept was done for Cache Full Api tests, so new test suite IgniteCacheFullApiMultiJvmSelfTestSuite
was added which contains test runners in multi-JVM mode.

Next tickets have been created in process of working on the ticket:

IGNITE-1107 Full Api Milti-JVM testLocalClearKeys test doesn't work for OFFHEAP_TIERED.	 
IGNITE-1113 GridCacheAtomicNearOnlyMultiJvmFullApiSelfTest.testEvictExpired fails	 
IGNITE-1088 (Multi jvm) Full api test which test store.	 
IGNITE-1089 (Multi jvm) Need to rewrite Full Api ttl tests.
IGNITE-1104 Need to implement GridCachePartitionedReloadAllAbstractSelfTest in multi-JVM mode.

IGNITE-1105 Need to implement GridCacheAbstractFullApiMultithreadedSelfTest in multi-JVM mode.

IGNITE-1112 Atomic cache #get method returns old value if near cache enabled after second
putAll.
IGNITE-1114 Need to implement GridCacheNearTxMultiNodeSelfTest in Multi-JVM mode	 
IGNITE-1115 Need to implement GridCachePartitionedMultiNodeCounterSelfTest in Multi-JVM mode

IGNITE-1116 Multi JVM unit tests framework should use demon node on local JVM
IGNITE-1117 Implement Cache Failover test in Multi-JVM mode 

There are tests which have strange behavior in multi-JVM mode and should be investigated:

IGNITE-1112 Atomic cache #get method returns old value if near cache enabled after second
putAll.
IGNITE-1107 Full Api Milti-JVM testLocalClearKeys test doesn't work for OFFHEAP_TIERED.	 
IGNITE-1113 GridCacheAtomicNearOnlyMultiJvmFullApiSelfTest.testEvictExpired fails	 

> Implement framework for multi JVM unit tests
> --------------------------------------------
>
>                 Key: IGNITE-648
>                 URL: https://issues.apache.org/jira/browse/IGNITE-648
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Yakov Zhdanov
>            Assignee: Artem Shutak
>            Priority: Critical
>             Fix For: sprint-7
>
>
> Now, Ignite test framework runs tests with multi ignite instances in one JVM.
> Need to improve Ignite test framework to have ability run different ignite instances
in separate JVMs.
> Ideally, it should be isMultiJvm() method, and if isMultiJvm() returns true, then framework
will run new grids by startGrid(...) methods in separate JVMs and existng tests have not to
be fully rewritten.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message