Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Sat, 11 Jul 2015 18:25:04 +0000 (UTC)
From: "James Carman (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12672337.1380894685000.162964.1436639104680@Atlassian.JIRA>
In-Reply-To: <JIRA.12672337.1380894685000@Atlassian.JIRA>
References: <JIRA.12672337.1380894685000@Atlassian.JIRA>
 <JIRA.12672337.1380894685640@arcas>
Subject: [jira] [Commented] (CAMEL-6826) Use Mock Objects Instead of Live
 HazelcastInstances to Speed Up Testing
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

James Carman commented on CAMEL-6826:
-------------------------------------

You mean it's fast enough after the changes made?  Sorry didn't realize this was the one with work already done.  If we like how it works now, I'm cool with closing this, but it should be marked as "fixed" since something was actually done.

> Use Mock Objects Instead of Live HazelcastInstances to Speed Up Testing
> -----------------------------------------------------------------------
>
>                 Key: CAMEL-6826
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6826
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-hazelcast
>            Reporter: James Carman
>
> The unit tests for the camel-hazelcast component use real HazelcastInstance objects, which is very slow.  We should use mock objects instead to speed up testing.  Testing the integration can be done with a few, select tests, but the majority of the logic can be tested with mocks.


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