I have maybe spoken too quickly.
I recently tried jmock 2 (not yet released), and I think they will
provide a good support for refactoring. I have also seen rMock
(http://rmock.sourceforge.net/).
We will have to wait a little bit, but there is maybe no reason for
nextmock to go into the direction of a.
By experimenting them, I have found an other area of intrest where
mock object might go further. I wonder how mock techniques and design
by contract might complement themself.
The characteristics of mock techniques is that :
- The desing is top down.
- Integration test are required to test the integration between modules.
- Provide only usefull classes
The design by contract is :
- Rather botom-up
- Requires less unit test because the integration test verify the
behavior of every class by checking the contracts.
- Provides complete/consistant classes
This seems at a first glance +/- complementary.
I wonder if it would be possible to include some pre/post condition
validation into mock object expectations. I also wonder if it is not
possible to find a refactoring (or refinment) path from mock
expectations to pre/post conditions.
At this point, it is just ideas. Feel free to think about it, and to
share your idea. If you are interrested, the nextmock project might
host some experimentation on the subject.
2007/1/18, Gilles Scokart <gsc...@gm...>:
>
>
> Nextmock is suspended (since a while already) because I a have too few time,
> and too few motivations to continue alone.
>
> I'm still convinced that the ideas are good. There is curently no mock
> tools supporting the level of refactoring that I would like to achieve.
>
> If you think also that the support of refactoring is an important feature of
> a mock tools, please contact me. And if you are interrested we could
> relaunch the project, or just discuss the ideas.
>
> Thanks,
>
>
> SCOKART Gilles
>
>
--
Gilles SCOKART
|
