Hi Mike Thanks for asking. I removed it because I had the impression it depends on the class XMLWriter that is not in the image. Looking at it again, I see that this is just example code to run the test on. If I change XMLWriter to Object the test run green. I will add it again.
Issue 1317: Add MethodHighlightingTests back http://code.google.com/p/pharo/issues/detail?id=1317 Adrian On Oct 17, 2009, at 11:47 , Michael Roberts wrote: > Hi Adrian > is method highlighting test broken or bogus? Was there a reason to not > mark it expected failure? > > Thanks > mike > > On Saturday, October 17, 2009, Adrian Lienhard <[email protected]> > wrote: >> Issue 1310: Make all tests green (not complete yet) >> - Remove class MethodHighlightingTests >> - ParseNode removeSelector: #addCommentToMorph: >> - Fix SelfEvaluatingObjectTest>>testArray ({1 + 0 . 1 @ 2 . 3}' >> prints >> '{1. 1...@2. 3}) >> - Remove method CompiledMethod>>primitiveNode as it is not used >> anymore >> - Fix toolbuilder tests (sort of) >> - Fix Decompiler>>decompileBlock: (regression of closure fixes). This >> makes BlockContextTest>>testDecompile pass again >> - Make BlockContextTest>>testTrace run by commenting out broken part >> of code simulation >> Issue 1308: FixedIdentitySet = fails when compared with an >> integer >> >> >> ___________________ >> http://www.adrian-lienhard.ch/ >> >> >> _______________________________________________ >> 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 _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
