Le 24/4/15 12:26, Christophe Demarey a écrit :
Le 22 avr. 2015 à 20:19, stepharo a écrit :
Christophe
I do not have the answer just the constraints.
This is hyper important that the solution does not change much SUnit.
This way we do not end up with a mess with Sunit version.
It is better to have a separate package.
I ckecked and we already diverged a lot from the SUnit standard (use of Traits,
announcements, etc.).
Do you want I integrate the refactoring to have the test selectors selection
coherent?
If yes, my proposal just adds 'or: [ selector name beginsWith: 'should' ]. I do
not see the point of having a separate package.
If no, does it mean that we should never touch the SUnit package?
No this is just that for now we do not express dependencies to a Sunit
package number :)
but when we will start to do it, it may be more complex.
I got some problems with SUnit and SUnitToo in VW. Not fun.
