I sent this to Mr. Leon, and this was his reply: You're not running the latest sUnit. Find and load sUnit Enhanced which has a better UI and includes these methods.
Bleh, DZ On Aug 17, 2009, at 3:45 PM, Daniel P Zepeda wrote: > Oh, so you guys are saying that this was a convenience selector that > was added in the image I was using which was never in Pharo. I hadn't > thought about that, I thought it had something to do with differences > in argument precedence, which seems to be a more basic issue between > Pharo and Squeak. Since I totally went with Pharo, I removed all of > the Squeak images I had, so I don't know if that convenience selector > was in the image I was using or not. > > If it was a convenience selector, I'm glad it was removed, I wouldn't > have expected that behavior. I guess I should just make a change set > and send it to Mr. Leon to do with what he wants to, as I said the > workaround is trivial. > > DZ > On Aug 17, 2009, at 11:45 AM, Adrian Lienhard wrote: > >> I quickly checked in Squeak 3.9 and 3.10 but they do not have that >> method either. So chances are high that this method never was in >> Pharo. Maybe it was added by some other package as an extension. >> >> Cheers, >> Adrian >> >> On Aug 17, 2009, at 18:32 , Henrik Sperre Johansen wrote: >> >>> I can't remember this change specifically, but to me it seems like a >>> method was removed from Pharo that just added slight syntactic >>> sugar. >>> I'd reckon the reasoning was that it was not in some "standard" >>> SUnit, >>> and thus keeping it lead to worse portability to Smalltalks other >>> that >>> Squeak. (For example, it does not exist in VisualWorks) >>> A case could be made that the method should have been deprecated >>> rather >>> than removed, but done is done, and all that :) >>> >>> Cheers, >>> Henry >>> >>> On 17.08.2009 18:17, Daniel P Zepeda wrote: >>>> Greetings, >>>> >>>> I've run across this in my own tests that ran fine in Squeak, but >>>> failed in Pharo. I thought it was just me being a dummy, but when I >>>> imported SandstoneDb and ran the tests, the exact same thing >>>> happens. >>>> It is a simple fix, but being fairly new at this, I'd like to know >>>> why >>>> this is, and if I should have to do this or not. >>>> >>>> So, for easy reference, I loaded the latest SandstoneDb (rjl.117) >>>> into >>>> my image (pharo1.0beta-10401web09.07.5) and ran the tests, several >>>> of >>>> which failed with a doesNotUnderstand: #assert:includes: >>>> >>>> Here is the test: >>>> >>>> testCollectionSerialization >>>> kid save. >>>> mom children: (OrderedCollection with: kid). >>>> mom save. >>>> self flushAndReload . >>>> self >>>> assert: mom refreshed children >>>> includes: kid refreshed >>>> >>>> if I simply put parens around the argument to assert: like this: >>>> >>>> assert: (mom refreshed children >>>> includes: kid refreshed) >>>> >>>> it passes. In all cases of failing tests with SandstoneDb, that is >>>> the >>>> case. Any insight here? >>>> >>>> Thanks! >>>> DZ >>>> > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
