[plt-scheme] Re: plt-scheme Digest, Vol 53, Issue 56

On 19 Jan 2010, at 8:23:22, plt-scheme-request at list.cs.brown.edu wrote:

> Message: 1
> Date: Tue, 19 Jan 2010 11:40:28 -0800
> From: John Clements <clements at brinckerhoff.org>
> Subject: [plt-scheme] check-expect exceptionalism bites again.
> To: PLT-Scheme Mailing List <plt-scheme at list.cs.brown.edu>
> Message-ID: <F54E93D3-1F6D-4262-BAD7-160A45705EA1 at brinckerhoff.org>
> Content-Type: text/plain; charset="us-ascii"
>
> I'm putting together a simple teach-yourself-scheme website--I'll  
> show more when I've got more to show--and the goofy evaluation rules  
> for check-expect have bitten me again. Specifically, sending (check- 
> expect 3 4) to an evaluator created with the sandbox evaluator  
> produces void, and presumably the check-expect is going onto a pile  
> to get evaluated "later".  Grr!
>
> Seems to me like it would be easier just to tell everyone to put  
> their darn test cases as the end of the program.
>
> Yes, in some sense this is yet another "top level is broken" comment.
>
> I can see two straightforward solutions that keep the world the way  
> it is:
> 1) create a "dont-delay-test-cases" parameter that--when set--would  
> cause test cases to expand into call-right-now test cases
> 2) create a "trigger-test-case-queue" function that would tell a  
> sandbox evaluator to go ahead and run its test cases.
>
> Either of these sound good / simple?  Is there a simpler solution?

There is (outside of the teaching languages) a function to trigger  
running the tests, provided by test-engine/scheme-tests -- (test); I  
could add a parameter to run the tests as soon as they're seen, if  
there's sufficient desire.

The results are unlikely to be displayed in a sandbox environment  
though, for which the test library needs to provide a better interface.

-Kathy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.racket-lang.org/users/archive/attachments/20100119/d141ad40/attachment.html>