what I gained in speed of tests I lost in readability of
>> the test cases for people that aren't fluent in mocking.
>> >
>> > Aspects are still a deep mystery to me. I know they can be terribly
>> useful but wow are they hard to read.
>> >
>> > I
ects are still a deep mystery to me. I know they can be terribly
> useful but wow are they hard to read.
> >
> > I can probably throw together a few quick mockito sample tests to get
> the ball rolling on this. After I look at some of the patch backlog.
> >
> > C
et the
> ball rolling on this. After I look at some of the patch backlog.
>
> C
>
> -Original Message-
> From: Mahadev Konar [mailto:maha...@hortonworks.com]
> Sent: Tuesday, November 01, 2011 12:52 AM
> To: dev@zookeeper.apache.org
> Subject: Re: Better testing
e.org
Subject: Re: Better testing for client code...
I am all for using mockito. I have found it very handy in writing good
unit tests. Our codebase needs little changes to be able to unit test
our codebase.
Writing a "real" unit test for the java client would be a good use
case to see wha
I am all for using mockito. I have found it very handy in writing good
unit tests. Our codebase needs little changes to be able to unit test
our codebase.
Writing a "real" unit test for the java client would be a good use
case to see what all changes need to happen on the client.
thanks
mahadev
I've been thinking that we need better testing for the client code. In
particular it's currently difficult to simulate all the different
types of failures a client might see. I'm wondering how we might do
this - two ideas come to mind; 1) aspectj and 2) mocks (mockito).
Anyone have other suggestion
