cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-250) Add mocking library to lib
Date Mon, 22 Jun 2009 14:31:07 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12722616#action_12722616
] 

Jonathan Ellis commented on CASSANDRA-250:
------------------------------------------

Commonly used utility classes are exactly the kind of thing you can test _without_ mocking.
 So no problem there.

> Add mocking library to lib
> --------------------------
>
>                 Key: CASSANDRA-250
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-250
>             Project: Cassandra
>          Issue Type: Task
>            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.


Mime
View raw message