[Pharo-dev] Unifying Testing Ideas

Frank Shearar frank.shearar at gmail.com
Wed Dec 4 05:31:21 EST 2013

On 4 December 2013 10:01, Attila Magyar <m.magyar3 at gmail.com> wrote:
> Sean P. DeNigris wrote
>> Are you interested in integrating my changes into the current API? If so,
>> I'll refactor them and clean them up. I personally would find it difficult
>> to use the library without them. Coming from Ruby, a proper test double
>> framework is the thing I miss most. Rspec was amazing. BabyMock is close,
>> and with these changes has the test double features I commonly relied on
>> Rspec for...
> Yes, anyArgs can be useful, and I was thinking about the /does/ extension
> too, and I convinced myself that it is ok and useful. I gave you access to
> the repo.
> The reason for my initial hesitation was that my goal is to not have too
> powerful features like rspec has. E.g. in rspec, it is easy to stub out
> global class objects and I see lots of ruby programmer doing it. I don't
> think this is the right solution for the problem.

Can you give an example of what you mean?

Being about to stub out the file system, or the clock, seem like
extremely useful things to do. (See https://github.com/defunkt/fakefs
for instance.)


More information about the Pharo-dev mailing list