Denis
We are working since 4 years now to get
- have a small kernel + tests
- be able to load nicely configurations
We should not add something else than Sunit for tests of the small
kernels tests.
Now people can use whatever they want to test their system but for the core
we are really picky because loading on single package may add far too
many dependencies.
and it means
- more time to load
- more time to debug
- more time to just understand what did not work during the bootstrap.
So our goal is to shrink the minimal core and not to extend it. So we
will add mock by hand if we need them.
I agree with Guillermo. Far too much pain.
Stef
Le 28/10/16 à 18:51, Denis Kudriashov a écrit :
We always said that smalltalk is the best for TDD.
But we not have mocks by default in Pharo while mocks is fundamental
part of TDD.
So no kernel tests could benefit from them.
And more important TDD is design process and without mocks we can't
apply it to kernel with full power.
What you think to integrate Mocketry in Pharo 6?
It has comments and documentation (PharoInProgress, Help), advanced
features and it is very competitive to any modern mock libraries.
Best regards,
Denis
