accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Vines (Updated) (JIRA)" <>
Subject [jira] [Updated] (ACCUMULO-14) Transition from fulll Accumulo mocking
Date Tue, 01 Nov 2011 18:31:33 GMT


John Vines updated ACCUMULO-14:

    Affects Version/s: 1.5.0
        Fix Version/s:     (was: 1.4.0)

This would be a great new feature for 1.5. I think for 1.4, since we're so close to wrapping
up on it, it's not worthwhile to undertake this effort as it could hold back release. I think
a full mocking would be great come then, giving plenty of time for it to be developed, as
well as for the rest of the community (really myself and most of the other comitters) to really
learn and understand the true benefits of Mocking.

So I think this should be bumped to 1.5 where it can be given serious consideration.
> Transition from fulll Accumulo mocking
> --------------------------------------
>                 Key: ACCUMULO-14
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: client
>    Affects Versions: 1.3.5, 1.4.0, 1.5.0
>            Reporter: Jesse Yates
>             Fix For: 1.5.0
> Original discussion present here:
> Jesse Yates: "Maintaining a real instance and a mock instance ends up creating a lot
of extra work for dev's by ensuring that there impls are kept synchronized....[using a real]
instance of Accumulo running on the local file system. This would mean less work in the long
run to maintain a separate instance and better testing for users and new features."
> Keith Turner: "its very fast to create a mock instance which means that unit test run
very quickly...[and] its all in process which is useful for debugging...making mock leverage
more of the actual accumulo code, but possibly keep it in process for speed and debugging."
> This ticket is to track the discussion and development of a less mocked test instance
of accumulo, that relies more heavily on the actual implementation, rather than parallel mocking

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message