Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 12 Jul 2016 09:15:21 +0000 (UTC)
From: "Stefan Podkowinski (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12979835.1466086583000.1013.1468314921108@Atlassian.JIRA>
In-Reply-To: <JIRA.12979835.1466086583000@Atlassian.JIRA>
References: <JIRA.12979835.1466086583000@Atlassian.JIRA> <JIRA.12979835.1466086583583@arcas>
Subject: [jira] [Updated] (CASSANDRA-12016) Create MessagingService mocking
 classes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 12 Jul 2016 09:15:23 -0000


     [ https://issues.apache.org/jira/browse/CASSANDRA-12016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Podkowinski updated CASSANDRA-12016:
-------------------------------------------
    Attachment: 12016-trunk.patch

> Create MessagingService mocking classes
> ---------------------------------------
>
>                 Key: CASSANDRA-12016
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12016
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Testing
>            Reporter: Stefan Podkowinski
>            Assignee: Stefan Podkowinski
>         Attachments: 12016-trunk.patch
>
>
> Interactions between clients and nodes in the cluster are taking place by exchanging messages through the {{MessagingService}}. Black box testing for message based systems is usually pretty easy, as we're just dealing with messages in/out. My suggestion would be to add tests that make use of this fact by mocking message exchanges via MessagingService. Given the right use case, this would turn out to be a much simpler and more efficient alternative for dtests.


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