Ensure is also used as part of the assertion framework. Maybe it
should stay as the core?
As for the Block interface, I believe it is because Runnable does not
declare any exception to throw. A minor plus is that the Block is a
little better named.
Cheers
Shane
On 12/5/06, Mauro Talevi <[EMAIL PROTECTED]> wrote:
Hi,
I was looking into making the mocking framework used by scenarios injectable.
I would:
- pull up to UsingMocks interface methods now found in UsingMiniMock,
UsingJMock ... eg
Mock mock(Class type);
Mock mock(Class type, String name);
Object stub(Class type);
Object stub(Class type, String name);
All mocking frameworks must be able to honour this interface.
- introduce a decorator impl of UsingMocks that delegates to specific
implementations - MiniMock,
JMock, etc ... - as a convenience base to subclass which is itself independent
of the mocking
framework.
While on the subject, I would also:
- move Ensure and UsingMocks interfaces to core.mock package - for consistency
with other packages.
- remove deprecated Verify
Finally
- any reason why we are using Block interface instead of standard JDK Runnable?
Comments? Objections?
Cheers
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
--
Shane
http://www.shaneduan.com
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
