hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Dunning <tdunn...@maprtech.com>
Subject Re: Mocking classes for unit tests Was: asynchbase-1.2.0-rc1 is available for download
Date Wed, 22 Feb 2012 21:25:23 GMT
Actually jmockit uses byte code patching so you may suffer less reflection overhead than expected.
My guess is that powermock is doing something quite similar. 

Sent from my iPhone

On Feb 22, 2012, at 9:29 AM, Jesse Yates <jesse.k.yates@gmail.com> wrote:

> Only long standing problem I've found with it is that, by necessity, almost
> everything is done via reflection, so method names to (power)mock need to
> be passed as strings, which can be annoying (but not hard) to maintain.
> +1 on adding in powermock as a best practice and updating the book to say
> so.

View raw message