Hi,
In general, we should distinguish between "development" and
"integration into pharo".
It makes no sense to harvest broken things. If sunit needs
improvement, start a sunit
improvement branch. Then, when it is stable, we can integrate.
And, we then have a chance to think if we actually want a change or not.
Marcus
On 08.11.2008, at 08:16, Stéphane Ducasse wrote:
I moved it into treatedInbox.
We cannot keep broken elements in the inobox, especially since
marcus or adrian or nicolas
may have a look at it again.
We do not have time for losing it three or four times.
For us this is really important that we keep it clean else we can
lose control.
anything that somebody put in treated inbox will end up either in
Is it clear?
If you try to do our job you will really fast see how it can get
frustrating
- not knowing what is a changes
- not knowing whether it works
- not knowing whether is works but breaks something else.
and taking responsibility for the mess we can put.
So take 2 min to think about that and you will see what we are doing
and why.
We can do an harvesting session with anybody so that we share the feel
Stef
On Nov 7, 2008, at 8:37 PM, Alexandre Bergel wrote:
When I load SUnit in pharoBox
There is no SUnit package in PharoInbox.
Are you referring to SUnitGUI-AlexandreBergel.15.mcz in Pharo?
Obviously we should not have saved this file in Pharo, but in
PharoInbox rather. I apologize for this.
SUnitGUI-AlexandreBergel.15.mcz expects the method
generateLastRunMethodNamed:for: to be present. This method is
provided by two packages that may be found in PharoTreatedInbox.
However there is something strange, the following method has
disappeared from the image (I tried with an Core 10133 updated):
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
TestResult>>runCase: aTestCase
| testCasePassed |
testCasePassed := true.
[[aTestCase runCase]
on: self class failure
do:
[:signal |
failures add: aTestCase.
testCasePassed := false.
signal return: false]]
on: self class error
do:
[:signal |
errors add: aTestCase.
testCasePassed := false.
signal return: false].
testCasePassed ifTrue: [passed add: aTestCase]
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Is there any reason for this? Our extension on storing results will
have to be updated then...
Alexandre
I cannot run tests anymore!
David Alex can you really check?
Guys I appreciate your work but it would be great if you could
test more
what you are doing because I spent a lot of time on problems like
that.
Stef
_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
--
Marcus Denker -- [EMAIL PROTECTED]
http://www.iam.unibe.ch/~denker
_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
