Coverage-SR.221.mcz To: Klaus D. Witzel
stefan_reichhart at students.unibe.ch
stefan_reichhart at students.unibe.ch
Thu Nov 16 12:14:19 UTC 2006
Hi Klaus,
I now tried several times to reply to your request from this morning,
but your or your (crazy) provider/company spam firewall does reject
just everything I try to send you ... so I hope you get my response
via this rather unusual way via squeak-dev-list ;) my reply is at
the bottom of this mail
Cheers,
Stef
On 16.11.2006, at 10:58, Klaus D. Witzel wrote:
> Ahoi Stefan,
>
> das hört sich ja sehr gut an (show coverage & test result at the
> same time). Hat es Beispiele auf SqueakSource / im package damit
> ich das mal life ansehen kann?
>
> Cheers
> Klaus
>
>> mondrian scripts enhanced -> class/method overview show coverage &
>> test result
>> at the same time
>> _________________________________________________________________
>>
>> Article:
>> * http://www.squeaksource.com/Coverage.html
>>
>> Download:
>> * http://www.squeaksource.com/Coverage/Coverage-SR.221.mcz
>
On 16.11.2006, at 12:23, MAILER-DAEMON wrote:
> Your message to: klaus.witzel at cobss.com
> was blocked by our Spam Firewall. The email you sent with the
> following subject has NOT BEEN DELIVERED:
>
> Subject: Re: Coverage-SR.221.mcz
>
> Reporting-MTA: dns; mxin.insystmail.de
> Received-From-MTA: smtp; mxin.insystmail.de ([127.0.0.1])
> Arrival-Date: Thu, 16 Nov 2006 12:23:21 +0100 (CET)
>
> Final-Recipient: rfc822; klaus.witzel at cobss.com
> Action: failed
> Status: 5.7.1
> Diagnostic-Code: smtp; 550 5.7.1 Message content rejected, UBE,
> id=07460-01-106
> Last-Attempt-Date: Thu, 16 Nov 2006 12:23:21 +0100 (CET)
> Received: from smtp.hispeed.ch (mxout.hispeed.ch [62.2.95.247])
> by mxin.insystmail.de (Spam Firewall) with ESMTP id 739E32001056
> for <klaus.witzel at cobss.com>; Thu, 16 Nov 2006 12:23:21 +0100 (CET)
> Received: from [192.168.1.101] (84-74-19-231.dclient.hispeed.ch
> [84.74.19.231])
> (authenticated bits=0)
> by smtp.hispeed.ch (8.12.11.20060308/8.12.6/taifun-1.0) with ESMTP
> id kAGATogw006843
> (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO);
> Thu, 16 Nov 2006 11:29:59 +0100
> In-Reply-To: <op.ti3sndlhrf0v61 at toshiba3>
> References: <139d675fd6c5a855068e4833fac42ace at rss.opera.com>
> <op.ti3sndlhrf0v61 at toshiba3>
> Mime-Version: 1.0 (Apple Message framework v752.2)
> Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
> Message-Id: <38EEBCD1-9818-442B-BA7B-C848814A61F4 at students.unibe.ch>
> Content-Transfer-Encoding: quoted-printable
> From: "stefan_reichhart at students.unibe.ch"
> <stefan_reichhart at students.unibe.ch>
> Subject: Re: Coverage-SR.221.mcz
> Date: Thu, 16 Nov 2006 11:29:48 +0100
> To: "Klaus D. Witzel" <klaus.witzel at cobss.com>
> X-Mailer: Apple Mail (2.752.2)
> X-Virus-Scanned: ClamAV version 0.88.6, clamav-milter version
> 0.88.6 on smtp-07.tornado.cablecom.ch
> X-Virus-Status: Clean
> X-DCC-spamcheck-02.tornado.cablecom.ch-Metrics:
> smtp-07.tornado.cablecom.ch 1378;
> Body=2 Fuz1=2 Fuz2=2
Hallo Klaus,
Ich habe (noch) kein "explizites Demopackage" erstellt - sollte ich
wirklich noch machen -, aber bisher funktioniert Christo mit allen
bekannten SqueakSource-Packages, mit Ausnahme von sich selbst (!),
sh. Case Studies, http://smallwiki.unibe.ch/stefanreichhart/
codecoverage/
Mögliche Demos:
- "Aconcagua" ist ein recht guter Demo-Kandidat, den ich gerne verwende
- In der Klassen-Kategorie "Coverage-IntelliDebug-TestResources" gibt
es ein paar Sourcen/Tests die sich ebenfalls eignen (da die Tests
failen), Sie zeigen Coverage & Failures/Errors und Passes, .....
Das Laden von "Christo" sollte mittlerweile eigentlich ziemlich
einfach sein - sofern NewCompiler etc funktionieren ...
--> "PackageLoader" (http://www.squeaksource.com/PackageLoader)-->
"CoverageLoader new loadAll"
(ich empfehle die Option ByteSurgeon, die funktioniert am Besten,
unbedingt in einem separaten Image arbeiten, man weiss ja nie)
PS: die Mondrian-Sachen sind noch recht experimentel
Gruss,
Stef
__________________________
http://www.reichhart.freezope.org
More information about the Squeak-dev
mailing list
|