Hi bryce

do you think that it would make sense to have it for the interpreter?
I do :). I contacted Dan because he told me that he fixed the 
interpreter
when doing the 64 port (but dan did not reply yet) and I would like to 
get
those fixes back in the image because I would like to learn by playing 
with
the interpreter and this is really a key asset of Squeak.

Stef


On 29 sept. 04, at 21:41, Bryce Kampjes wrote:

> Alan Grimes writes:
>> I have been taking a class in software engineering, One of the only
>> useful lessons to come out of the course is about test coverage.
>>
>> So I compiled my VM with full test coverage (dude). =P
>>
>> I fired up this VM and ran the full SM tests with the benchmarks.
>>
>> When I looked at the output, I found that most source lines had been
>> executed so many times the counters rolled over!
>
> I have a test suite that covers most of the interpreter fairly
> systematically. It is currently targeted at Exupery but if you
> make the compile methods null ops then it would test the interpreter.
>
> Most of it tests each individual byte code going through all the
> edge cases.
>
> It's available via SqueakMap and SqueakSource.
>
> Bryce
>