Hi Denis,

I've commited Mocketry-Help and ConfigurationOfMocketry is in MetacelloRepository.

I removed SMock-SUnit from the Configuration but SMock is still here for Mocketry-Tests (it may be good enough for a first release).


I have 3 tests failing from SMock:

SMProxyTest>>#testDefaultInspectString
SMProxyTest>>#testDefaultDebugString
SMProxyTest>>#testDefaultPrintString


Cheers,

Laurent.


On Tue, Nov 30, 2010 at 9:15 AM, Denis Kudriashov <dionisiydk@gmail.com> wrote:


2010/11/30 laurent laffont <laurent.laffont@gmail.com>


On Mon, Nov 29, 2010 at 10:20 PM, Denis Kudriashov <dionisiydk@gmail.com> wrote:
Hello, I am very glad to your work.

I try configuration in pharo1.1. Loaded without problem. And Mocketry tests green.

Why you add SMock to Core group?

Because I'm ignorant :) ��What is SMock exactly ?


SMock is primitive mocks framework that I use for Mocketry development. Only MocketryTests depends on SMock.

��
Indeed I've never used Mocketry but I want to package existing mocking frameworks for Pharo.
��
SMock only needed for MocketryTests. And if you need mocks just use Mocketry.
I think SMock should has separate configuration

You mean ConfigurationOfSMock ?
��

Yes.
��