test coverage works correctly for these three programs: (define (f x) x)
--- (define (f x) x) (f 1) --- (define (f x) x) (check-expect (f 1) 1) On Mon, May 11, 2009 at 6:33 AM, Matthias Felleisen <matth...@ccs.neu.edu> wrote: > > How about the coverage bug (point 2, below)? > > On May 11, 2009, at 7:14 AM, Robby Findler wrote: > >> I didn't fix anything, so I'm cc'ing plt-dev in case the person who >> did is there. >> >> Robby >> >> On Sunday, May 10, 2009, Matthias Felleisen <matth...@ccs.neu.edu> wrote: >>> >>> Correct. It went away with an update. (I had thursday's drscheme >>> running.) >>> >>> BUT, now I am getting this >>> >>> >>> [:~/svn/2HtDP/SampleCode] matthias% (display-reason #<unequal> #t #f) >>> (display-reason #<unequal> #t #f) >>> (display-reason #<unequal> #t #f) >>> (display-reason #<unequal> #t #f) >>> (display-reason #<unequal> #t #f) >>> (display-reason #<unequal> #t #f) >>> (display-reason #<unequal> #t #f) >>> (display-reason #<unequal> #t #f) >>> (display-reason #<unequal> #t #f) >>> (display-reason #<unequal> #t #f) >>> (display-reason #<unequal> #t #f) >>> (display-reason #<unequal> #t #f) >>> (display-reason #<unequal> #t #f) >>> >>> >>> in the console from where I launched drscheme. >>> >>> AND, I am getting the names of the functions colored as if they hadn't >>> been run, even though my test cases provide complete coverage. >>> >>> >>> >>> On May 10, 2009, at 5:55 PM, Robby Findler wrote: >>> >>> >>> I just tried to look into this, but the program you sent (when running >>> in BSL + universe.ss with a build from a few hours ago) does not >>> trigger the bug for me. >>> >>> Robby >>> >>> >>> > > _________________________________________________ For list-related administrative tasks: http://list.cs.brown.edu/mailman/listinfo/plt-dev
