Jesse Yates 2012-09-15, 02:16
lars hofhansl 2012-09-15, 04:13
Andrew Purtell 2012-09-15, 19:11
Stack 2012-09-15, 20:14
-Re: testing, powermock, jmockit - from pow-wow
Andrew Purtell 2012-09-15, 20:40
We have interface annotations and @VisibleForTesting?
Where we need to get to non HBase non public scoped fields or methods, then
reflection or judicious use of something like powermock just to expose
what's needed is a wash I'd say.
On Saturday, September 15, 2012, Stack wrote:
> > Perhaps the best course of action for test failures involving twisty code
> > weaving / alternate class loaders / multiple mocking libraries would be
> > svn rm or @Ignore.
> > We should consider that time and contributor bandwidth
> > is precious in a volunteer project, especially where unit tests are
> > concerned. If it's not possible to understand a unit test failure from
> > source given an exception and stack trace, the test itself is the
> You have a point Andrew.
> But how then to test the out-of-reach guts of HBase? You are not
> saying don't I'm sure. You think that exposing a method just for
> test use is reason enough for making a method public (a motive we've
> had sort-off up to this?)
Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)
Stack 2012-09-15, 03:34
Ted Yu 2012-09-15, 02:59