You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Michael Greene (JIRA)" <ji...@apache.org> on 2009/08/12 03:12:17 UTC
[jira] Updated: (CASSANDRA-250) Add mocking library to lib
[ https://issues.apache.org/jira/browse/CASSANDRA-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Greene updated CASSANDRA-250:
-------------------------------------
Component/s: Core
> Add mocking library to lib
> --------------------------
>
> Key: CASSANDRA-250
> URL: https://issues.apache.org/jira/browse/CASSANDRA-250
> Project: Cassandra
> Issue Type: Task
> Components: Core
> Reporter: Johan Oskarsson
> Priority: Trivial
> Fix For: 0.4
>
> Attachments: mockito-all-1.7.jar
>
>
> Cassandra in it's current state can be hard to write unit tests for, the classes are tightly coupled, a lot of variables and code is static. For example some 10 threads start up when you call a static method on MessagingService, even though all that method does is convert a byte array to a short.
> Should we make use of a mocking library to help us make it easier to write certain tests?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.