New spying feature about mockito HOT 9 CLOSED

Looks really good.

How would @Spy annotation work? Is it going to create an object based on a 
default
constructor? To make it consistent spy() method should also allow for:

Foo spy = Mockito.spy(Foo.class);

Ok then, @Spy annotation is out of the game. Let's not complicate and leave out 
the
default constructors.

I was thinking about possible scenarios for partial mocking and my conclusion 
is that
the usage of a proposal would be limited. Why? Because it won't allow you to 
stub
private methods and in most of my cases this is what I would like to do.

mocking private methods? You're a bad boy. When the test starts to be curious 
about a
private method then clearly this method should not be private any more :)

Implemented in 1.5