Re: [racket-users] DrRacket Coverage

[Greg Hendershott]

No.

But I color only the foreground, if I'm understanding your question.

On Tue, Feb 16, 2016 at 10:13 PM, Robby Findler
 wrote:
> Thanks. That makes sense. Did you discount white space?
>
> Robby
>
>
> On Tuesday, February 16, 2016, Greg Hendershott 
> wrote:
>>
>> 1.
>>
>> It's been awhile since I worked on this, but: I wanted my Racket code
>> to consolidate overlapping uncovered ranges into the simplest coloring
>> to-do list to report back to Emacs. And since that's what's visually
>> apparent to the user (regions colored red), I use the same count in
>> the message.
>>
>>
>> On Tue, Feb 16, 2016 at 9:22 AM, Robby Findler
>>  wrote:
>> > I'm sorry: that was a bit too telegraphic. I'm asking if the program
>> > below counts as one or some other number of uncovered regions. And
>> > things like that. I'm going to go with 1 here but another approach
>> > would be to show a percentage covered based on characters or
>> > something.
>> >
>> > Robby
>> >
>> > #lang racket
>> > (define-syntax (m stx)
>> >   (syntax-case stx ()
>> > [(_ a b c)
>> >  #`(void (λ () #,(datum->syntax #'here '(void) stx))
>> >  #,(datum->syntax #'here '(void) #'b))]))
>> >
>> > (m abcdef
>> >ghijkl
>> >mnopqr)
>> >
>> > On Tue, Feb 16, 2016 at 7:59 AM, Robby Findler
>> >  wrote:
>> >> How do you do this count? (what algorithm?)
>> >>
>> >> Robby
>> >>
>> >> On Tue, Feb 16, 2016 at 6:56 AM, Greg Hendershott
>> >>  wrote:
>> >>> FWIW when you run tests with coverage in racket-mode (C-u C-c C-t)
>> >>> displays in the echo area either "Coverge complete" or "Missing
>> >>> coverage in N places".  In the latter case, point moves to the first
>> >>> place. All such places are colored in red.
>> >>>
>> >>> One thing racket-mode should probably also do is have next-error to
>> >>> jump to later spots (if any). However I figured people would add
>> >>> coverage one spot at a time, so it didn't seem super compelling.
>> >>>
>> >>>
>> >>> On Tue, Feb 16, 2016 at 6:21 AM, Eli Barzilay 
>> >>> wrote:
>>  Re leaving the coverage colors: for the purpose of my class that
>>  would
>>  do fine, but for actual use, the lack of full coverage indication
>>  means
>>  that you'll need to scroll through the text to find out if you have
>>  it
>>  or not...
>> 
>>  So something like a status bar message would be better, either with
>>  leaving the coverage colors or not.  Even better if it "jumps up" as
>>  John said, so that it draws attention to it.
>> 
>>  --
>>  ((x=>x(x))(x=>x(x)))   Eli
>>  Barzilay:
>>  http://barzilay.org/   Maze is
>>  Life!
>> 
>>  --
>>  You received this message because you are subscribed to the Google
>>  Groups "Racket Users" group.
>>  To unsubscribe from this group and stop receiving emails from it,
>>  send an email to racket-users+unsubscr...@googlegroups.com.
>>  For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [racket-users] DrRacket Coverage

[Robby Findler]

Thanks. That makes sense. Did you discount white space?

Robby

On Tuesday, February 16, 2016, Greg Hendershott 
wrote:

> 1.
>
> It's been awhile since I worked on this, but: I wanted my Racket code
> to consolidate overlapping uncovered ranges into the simplest coloring
> to-do list to report back to Emacs. And since that's what's visually
> apparent to the user (regions colored red), I use the same count in
> the message.
>
>
> On Tue, Feb 16, 2016 at 9:22 AM, Robby Findler
> > wrote:
> > I'm sorry: that was a bit too telegraphic. I'm asking if the program
> > below counts as one or some other number of uncovered regions. And
> > things like that. I'm going to go with 1 here but another approach
> > would be to show a percentage covered based on characters or
> > something.
> >
> > Robby
> >
> > #lang racket
> > (define-syntax (m stx)
> >   (syntax-case stx ()
> > [(_ a b c)
> >  #`(void (λ () #,(datum->syntax #'here '(void) stx))
> >  #,(datum->syntax #'here '(void) #'b))]))
> >
> > (m abcdef
> >ghijkl
> >mnopqr)
> >
> > On Tue, Feb 16, 2016 at 7:59 AM, Robby Findler
> > > wrote:
> >> How do you do this count? (what algorithm?)
> >>
> >> Robby
> >>
> >> On Tue, Feb 16, 2016 at 6:56 AM, Greg Hendershott
> >> > wrote:
> >>> FWIW when you run tests with coverage in racket-mode (C-u C-c C-t)
> >>> displays in the echo area either "Coverge complete" or "Missing
> >>> coverage in N places".  In the latter case, point moves to the first
> >>> place. All such places are colored in red.
> >>>
> >>> One thing racket-mode should probably also do is have next-error to
> >>> jump to later spots (if any). However I figured people would add
> >>> coverage one spot at a time, so it didn't seem super compelling.
> >>>
> >>>
> >>> On Tue, Feb 16, 2016 at 6:21 AM, Eli Barzilay  > wrote:
>  Re leaving the coverage colors: for the purpose of my class that would
>  do fine, but for actual use, the lack of full coverage indication
> means
>  that you'll need to scroll through the text to find out if you have it
>  or not...
> 
>  So something like a status bar message would be better, either with
>  leaving the coverage colors or not.  Even better if it "jumps up" as
>  John said, so that it draws attention to it.
> 
>  --
>  ((x=>x(x))(x=>x(x)))   Eli
> Barzilay:
>  http://barzilay.org/   Maze is
> Life!
> 
>  --
>  You received this message because you are subscribed to the Google
> Groups "Racket Users" group.
>  To unsubscribe from this group and stop receiving emails from it,
> send an email to racket-users+unsubscr...@googlegroups.com .
>  For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [racket-users] DrRacket Coverage

[Greg Hendershott]

1.

It's been awhile since I worked on this, but: I wanted my Racket code
to consolidate overlapping uncovered ranges into the simplest coloring
to-do list to report back to Emacs. And since that's what's visually
apparent to the user (regions colored red), I use the same count in
the message.


On Tue, Feb 16, 2016 at 9:22 AM, Robby Findler
 wrote:
> I'm sorry: that was a bit too telegraphic. I'm asking if the program
> below counts as one or some other number of uncovered regions. And
> things like that. I'm going to go with 1 here but another approach
> would be to show a percentage covered based on characters or
> something.
>
> Robby
>
> #lang racket
> (define-syntax (m stx)
>   (syntax-case stx ()
> [(_ a b c)
>  #`(void (λ () #,(datum->syntax #'here '(void) stx))
>  #,(datum->syntax #'here '(void) #'b))]))
>
> (m abcdef
>ghijkl
>mnopqr)
>
> On Tue, Feb 16, 2016 at 7:59 AM, Robby Findler
>  wrote:
>> How do you do this count? (what algorithm?)
>>
>> Robby
>>
>> On Tue, Feb 16, 2016 at 6:56 AM, Greg Hendershott
>>  wrote:
>>> FWIW when you run tests with coverage in racket-mode (C-u C-c C-t)
>>> displays in the echo area either "Coverge complete" or "Missing
>>> coverage in N places".  In the latter case, point moves to the first
>>> place. All such places are colored in red.
>>>
>>> One thing racket-mode should probably also do is have next-error to
>>> jump to later spots (if any). However I figured people would add
>>> coverage one spot at a time, so it didn't seem super compelling.
>>>
>>>
>>> On Tue, Feb 16, 2016 at 6:21 AM, Eli Barzilay  wrote:
 Re leaving the coverage colors: for the purpose of my class that would
 do fine, but for actual use, the lack of full coverage indication means
 that you'll need to scroll through the text to find out if you have it
 or not...

 So something like a status bar message would be better, either with
 leaving the coverage colors or not.  Even better if it "jumps up" as
 John said, so that it draws attention to it.

 --
 ((x=>x(x))(x=>x(x)))   Eli Barzilay:
 http://barzilay.org/   Maze is Life!

 --
 You received this message because you are subscribed to the Google Groups 
 "Racket Users" group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to racket-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [racket-users] DrRacket Coverage

['John Clements' via Racket Users]

> On Feb 16, 2016, at 6:48 AM, Robby Findler  
> wrote:
> 
> Anyway, I pushed something that matches the predicate that's already
> implemented, reflecting it into the GUI. It probably doesn't bounce as
> much as Eli & John hope, but maybe it is okay for now.
> 
> Robby
> 

Looking forward to seeing it. Thanks!

John



-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [racket-users] DrRacket Coverage

[Robby Findler]

Okay, this seems complex. I think I'll put that off until another day
as well. Here's where I got bogged down. When I run this program:

#lang racket/base
(define (f x)
  (+ xx
 xx
 xx
 xx
 xx))


the answer should probably be "one uncovered expression" but the data
I have to work with is this:

(#f #(struct:srcloc #(struct:object:...ivate/get-extend.rkt:134:12
...) #f #f 38 1))
(#t #(struct:srcloc #(struct:object:...ivate/get-extend.rkt:134:12
...) #f #f 28 1))
(#f #(struct:srcloc #(struct:object:...ivate/get-extend.rkt:134:12
...) #f #f 79 1))
(#f #(struct:srcloc #(struct:object:...ivate/get-extend.rkt:134:12
...) #f #f 36 1))
(#f #(struct:srcloc #(struct:object:...ivate/get-extend.rkt:134:12
...) #f #f 47 1))
(#f #(struct:srcloc #(struct:object:...ivate/get-extend.rkt:134:12
...) #f #f 95 1))
(#f #(struct:srcloc #(struct:object:...ivate/get-extend.rkt:134:12
...) #f #f 86 1))
(#f #(struct:srcloc #(struct:object:...ivate/get-extend.rkt:134:12
...) #f #f 63 1))
(#f #(struct:srcloc #(struct:object:...ivate/get-extend.rkt:134:12
...) #f #f 70 1))
(#f #(struct:srcloc #(struct:object:...ivate/get-extend.rkt:134:12
...) #f #f 54 1))
(#f #(struct:srcloc #(struct:object:...ivate/get-extend.rkt:134:12
...) #f #f 111 1))
(#f #(struct:srcloc #(struct:object:...ivate/get-extend.rkt:134:12
...) #f #f 35 78))
(#f #(struct:srcloc #(struct:object:...ivate/get-extend.rkt:134:12
...) #f #f 102 1))
(#t #(struct:srcloc #(struct:object:...ivate/get-extend.rkt:134:12
...) #f #f 19 95))
(#t #(struct:srcloc #(struct:object:...ivate/get-extend.rkt:134:12
...) #f #f 1 122))

Anyway, I pushed something that matches the predicate that's already
implemented, reflecting it into the GUI. It probably doesn't bounce as
much as Eli & John hope, but maybe it is okay for now.

Robby




On Tue, Feb 16, 2016 at 8:22 AM, Robby Findler
 wrote:
> I'm sorry: that was a bit too telegraphic. I'm asking if the program
> below counts as one or some other number of uncovered regions. And
> things like that. I'm going to go with 1 here but another approach
> would be to show a percentage covered based on characters or
> something.
>
> Robby
>
> #lang racket
> (define-syntax (m stx)
>   (syntax-case stx ()
> [(_ a b c)
>  #`(void (λ () #,(datum->syntax #'here '(void) stx))
>  #,(datum->syntax #'here '(void) #'b))]))
>
> (m abcdef
>ghijkl
>mnopqr)
>
> On Tue, Feb 16, 2016 at 7:59 AM, Robby Findler
>  wrote:
>> How do you do this count? (what algorithm?)
>>
>> Robby
>>
>> On Tue, Feb 16, 2016 at 6:56 AM, Greg Hendershott
>>  wrote:
>>> FWIW when you run tests with coverage in racket-mode (C-u C-c C-t)
>>> displays in the echo area either "Coverge complete" or "Missing
>>> coverage in N places".  In the latter case, point moves to the first
>>> place. All such places are colored in red.
>>>
>>> One thing racket-mode should probably also do is have next-error to
>>> jump to later spots (if any). However I figured people would add
>>> coverage one spot at a time, so it didn't seem super compelling.
>>>
>>>
>>> On Tue, Feb 16, 2016 at 6:21 AM, Eli Barzilay  wrote:
 Re leaving the coverage colors: for the purpose of my class that would
 do fine, but for actual use, the lack of full coverage indication means
 that you'll need to scroll through the text to find out if you have it
 or not...

 So something like a status bar message would be better, either with
 leaving the coverage colors or not.  Even better if it "jumps up" as
 John said, so that it draws attention to it.

 --
 ((x=>x(x))(x=>x(x)))   Eli Barzilay:
 http://barzilay.org/   Maze is Life!

 --
 You received this message because you are subscribed to the Google Groups 
 "Racket Users" group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to racket-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [racket-users] DrRacket Coverage

[Robby Findler]

That sounds quite nice, actually. But I think I'll leave that for another day.

Robby

On Tue, Feb 16, 2016 at 8:00 AM, Eli Barzilay  wrote:
> On Tue, Feb 16, 2016 at 7:56 AM, Greg Hendershott
>  wrote:
>> FWIW when you run tests with coverage in racket-mode (C-u C-c C-t)
>> displays in the echo area either "Coverge complete" or "Missing
>> coverage in N places".  In the latter case, point moves to the first
>> place. All such places are colored in red.
>>
>> One thing racket-mode should probably also do is have next-error to
>> jump to later spots (if any). However I figured people would add
>> coverage one spot at a time, so it didn't seem super compelling.
>
> Actually, this is another idea: the coverage facility tweaks the code
> anyway (through errortrace), so it can also add an expression at the end
> of the `test` submodule that throws an error with sources pointing at
> all of the uncovered expressions.  It's more extreme, but it makes many
> things work automatically -- for example, the handin server won't need
> to explicitly check for coverage, just run the code and throw any errors
> back to the client...
>
> --
> ((x=>x(x))(x=>x(x)))   Eli Barzilay:
> http://barzilay.org/   Maze is Life!

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [racket-users] DrRacket Coverage

[Robby Findler]

I'm sorry: that was a bit too telegraphic. I'm asking if the program
below counts as one or some other number of uncovered regions. And
things like that. I'm going to go with 1 here but another approach
would be to show a percentage covered based on characters or
something.

Robby

#lang racket
(define-syntax (m stx)
  (syntax-case stx ()
[(_ a b c)
 #`(void (λ () #,(datum->syntax #'here '(void) stx))
 #,(datum->syntax #'here '(void) #'b))]))

(m abcdef
   ghijkl
   mnopqr)

On Tue, Feb 16, 2016 at 7:59 AM, Robby Findler
 wrote:
> How do you do this count? (what algorithm?)
>
> Robby
>
> On Tue, Feb 16, 2016 at 6:56 AM, Greg Hendershott
>  wrote:
>> FWIW when you run tests with coverage in racket-mode (C-u C-c C-t)
>> displays in the echo area either "Coverge complete" or "Missing
>> coverage in N places".  In the latter case, point moves to the first
>> place. All such places are colored in red.
>>
>> One thing racket-mode should probably also do is have next-error to
>> jump to later spots (if any). However I figured people would add
>> coverage one spot at a time, so it didn't seem super compelling.
>>
>>
>> On Tue, Feb 16, 2016 at 6:21 AM, Eli Barzilay  wrote:
>>> Re leaving the coverage colors: for the purpose of my class that would
>>> do fine, but for actual use, the lack of full coverage indication means
>>> that you'll need to scroll through the text to find out if you have it
>>> or not...
>>>
>>> So something like a status bar message would be better, either with
>>> leaving the coverage colors or not.  Even better if it "jumps up" as
>>> John said, so that it draws attention to it.
>>>
>>> --
>>> ((x=>x(x))(x=>x(x)))   Eli Barzilay:
>>> http://barzilay.org/   Maze is Life!
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups 
>>> "Racket Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to racket-users+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [racket-users] DrRacket Coverage

[Eli Barzilay]

On Tue, Feb 16, 2016 at 7:56 AM, Greg Hendershott
 wrote:
> FWIW when you run tests with coverage in racket-mode (C-u C-c C-t)
> displays in the echo area either "Coverge complete" or "Missing
> coverage in N places".  In the latter case, point moves to the first
> place. All such places are colored in red.
>
> One thing racket-mode should probably also do is have next-error to
> jump to later spots (if any). However I figured people would add
> coverage one spot at a time, so it didn't seem super compelling.

Actually, this is another idea: the coverage facility tweaks the code
anyway (through errortrace), so it can also add an expression at the end
of the `test` submodule that throws an error with sources pointing at
all of the uncovered expressions.  It's more extreme, but it makes many
things work automatically -- for example, the handin server won't need
to explicitly check for coverage, just run the code and throw any errors
back to the client...

-- 
((x=>x(x))(x=>x(x)))   Eli Barzilay:
http://barzilay.org/   Maze is Life!

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [racket-users] DrRacket Coverage

[Robby Findler]

How do you do this count? (what algorithm?)

Robby

On Tue, Feb 16, 2016 at 6:56 AM, Greg Hendershott
 wrote:
> FWIW when you run tests with coverage in racket-mode (C-u C-c C-t)
> displays in the echo area either "Coverge complete" or "Missing
> coverage in N places".  In the latter case, point moves to the first
> place. All such places are colored in red.
>
> One thing racket-mode should probably also do is have next-error to
> jump to later spots (if any). However I figured people would add
> coverage one spot at a time, so it didn't seem super compelling.
>
>
> On Tue, Feb 16, 2016 at 6:21 AM, Eli Barzilay  wrote:
>> Re leaving the coverage colors: for the purpose of my class that would
>> do fine, but for actual use, the lack of full coverage indication means
>> that you'll need to scroll through the text to find out if you have it
>> or not...
>>
>> So something like a status bar message would be better, either with
>> leaving the coverage colors or not.  Even better if it "jumps up" as
>> John said, so that it draws attention to it.
>>
>> --
>> ((x=>x(x))(x=>x(x)))   Eli Barzilay:
>> http://barzilay.org/   Maze is Life!
>>
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "Racket Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to racket-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [racket-users] DrRacket Coverage

[Greg Hendershott]

FWIW when you run tests with coverage in racket-mode (C-u C-c C-t)
displays in the echo area either "Coverge complete" or "Missing
coverage in N places".  In the latter case, point moves to the first
place. All such places are colored in red.

One thing racket-mode should probably also do is have next-error to
jump to later spots (if any). However I figured people would add
coverage one spot at a time, so it didn't seem super compelling.


On Tue, Feb 16, 2016 at 6:21 AM, Eli Barzilay  wrote:
> Re leaving the coverage colors: for the purpose of my class that would
> do fine, but for actual use, the lack of full coverage indication means
> that you'll need to scroll through the text to find out if you have it
> or not...
>
> So something like a status bar message would be better, either with
> leaving the coverage colors or not.  Even better if it "jumps up" as
> John said, so that it draws attention to it.
>
> --
> ((x=>x(x))(x=>x(x)))   Eli Barzilay:
> http://barzilay.org/   Maze is Life!
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Racket Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to racket-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [racket-users] DrRacket Coverage

[Eli Barzilay]

Re leaving the coverage colors: for the purpose of my class that would
do fine, but for actual use, the lack of full coverage indication means
that you'll need to scroll through the text to find out if you have it
or not...

So something like a status bar message would be better, either with
leaving the coverage colors or not.  Even better if it "jumps up" as
John said, so that it draws attention to it.

-- 
((x=>x(x))(x=>x(x)))   Eli Barzilay:
http://barzilay.org/   Maze is Life!

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [racket-users] DrRacket Coverage

['John Clements' via Racket Users]

> On Feb 15, 2016, at 7:49 PM, Robby Findler  
> wrote:
> 
> I feel like a bar in the drracket window is a better choice than a
> printout in the REPL and I've half implemented it, but it feels like
> the message is a bit too far away. What do you think of these
> screenshots?
> 
> http://www.eecs.northwestern.edu/~robby/tmp/a.png
> 
> http://www.eecs.northwestern.edu/~robby/tmp/b.png
> 
> Is the bar on the bottom too subtle?

Does the message appear, making the bottom of the buffer jump? In this case, I 
think that would be a good thing, and draw attention to the message.

John

> 
> Robby
> 
> On Mon, Feb 15, 2016 at 4:05 PM, 'John Clements' via Racket Users
>  wrote:
>> 
>>> On Feb 15, 2016, at 2:00 PM, Robby Findler  
>>> wrote:
>>> 
>>> I mean (c). I think (b) means "nothing ran" (right?). And I'm asking
>>> if (c) is preferable to adding a "congrats!" note to the current
>>> behavior.
>>> 
>>> And I'm asking this as two questions, one about "the racket language"
>>> and one about the HtDP languages.
>> 
>> In my mind, (c) (all black) looks slightly un-festive and punitive. That may 
>> just be because I’ve thoroughly internalized the current scheme, though. I 
>> think I would apply this change to both the HtDP languages and the “the 
>> racket language” language, though I think the case is stronger for the HtDP 
>> languages (in that they are used more often by students who have a harder 
>> time figuring things like this out).
>> 
>> John
>> 
>>> 
>>> Robby
>>> 
>>> On Mon, Feb 15, 2016 at 3:50 PM, 'John Clements' via Racket Users
>>>  wrote:
 
> On Feb 15, 2016, at 1:24 PM, Robby Findler  
> wrote:
> 
> Do you also prefer that to just showing everything colored?
 
 To make sure I understand you (or the reverse); I’m suggesting that for a 
 correctly covered program, the resulting program would be colored in the 
 same way that it currently is for a correctly colored program (which 
 AFAICT is the same as the coloring before the program is run), and that a 
 line would be added to the interactions window. This seems like it would 
 be less work and less potentially irritating than a recurring (albeit 
 disable-able) dialog, though of course by the same token it probably makes 
 it somewhat more likely that students will miss it.
 
 Once again, this is not a major problem for my students, and I don’t think 
 it costs my students much sleep. (Honestly, pixel-level whizzy scrolling 
 would be a much bigger deal for them.)
 
 John
 
 (obconfusion explanation: When you say “showing everything colored,” I’m 
 not sure whether you mean (a) everything colored as it currently is, (b) 
 everything in orange with black highlighting, or (c) everything in black.)
> 
 
> Robby
> 
> 
> On Mon, Feb 15, 2016 at 3:06 PM, 'John Clements' via Racket Users
>  wrote:
>>> 
>>> I think that by the time they work hard to cover everything and the
>>> coverage colors disappear they quickly jump to a conclusion that
>>> something is wrong.  -- I even have the server report to them about
>>> uncovered code, but even that doesn't help.
>>> 
>>> In case it wasn't clear -- this is not too important, just something
>>> that strikes me as weird every time another student gets confused.
>> 
>> +1 to all of the above. I generally have to explain this to four or five 
>> students in each class.
>> 
>> What if a one-line message appeared in the interactions window, just 
>> after the version information?
>> 
>> John
>> 
>> 
>> 
>> --
>> You received this message because you are subscribed to the Google 
>> Groups "Racket Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send 
>> an email to racket-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> --
> You received this message because you are subscribed to the Google Groups 
> "Racket Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to racket-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
 
 
 
 --
 You received this message because you are subscribed to the Google Groups 
 "Racket Users" group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to racket-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.
>> 
>> 
>> 
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "Racket Users" group.
>> To unsubscribe from this group and 

Re: [racket-users] DrRacket Coverage

[Robby Findler]

Oh and I should add that I plan to add a "show next time" checkbox to the
bar, if the bar seems worth continuing with.

Robby

On Monday, February 15, 2016, Robby Findler 
wrote:

> I feel like a bar in the drracket window is a better choice than a
> printout in the REPL and I've half implemented it, but it feels like
> the message is a bit too far away. What do you think of these
> screenshots?
>
> http://www.eecs.northwestern.edu/~robby/tmp/a.png
>
> http://www.eecs.northwestern.edu/~robby/tmp/b.png
>
> Is the bar on the bottom too subtle?
>
> Robby
>
> On Mon, Feb 15, 2016 at 4:05 PM, 'John Clements' via Racket Users
> > wrote:
> >
> >> On Feb 15, 2016, at 2:00 PM, Robby Findler  > wrote:
> >>
> >> I mean (c). I think (b) means "nothing ran" (right?). And I'm asking
> >> if (c) is preferable to adding a "congrats!" note to the current
> >> behavior.
> >>
> >> And I'm asking this as two questions, one about "the racket language"
> >> and one about the HtDP languages.
> >
> > In my mind, (c) (all black) looks slightly un-festive and punitive. That
> may just be because I’ve thoroughly internalized the current scheme,
> though. I think I would apply this change to both the HtDP languages and
> the “the racket language” language, though I think the case is stronger for
> the HtDP languages (in that they are used more often by students who have a
> harder time figuring things like this out).
> >
> > John
> >
> >>
> >> Robby
> >>
> >> On Mon, Feb 15, 2016 at 3:50 PM, 'John Clements' via Racket Users
> >> > wrote:
> >>>
>  On Feb 15, 2016, at 1:24 PM, Robby Findler <
> ro...@eecs.northwestern.edu > wrote:
> 
>  Do you also prefer that to just showing everything colored?
> >>>
> >>> To make sure I understand you (or the reverse); I’m suggesting that
> for a correctly covered program, the resulting program would be colored in
> the same way that it currently is for a correctly colored program (which
> AFAICT is the same as the coloring before the program is run), and that a
> line would be added to the interactions window. This seems like it would be
> less work and less potentially irritating than a recurring (albeit
> disable-able) dialog, though of course by the same token it probably makes
> it somewhat more likely that students will miss it.
> >>>
> >>> Once again, this is not a major problem for my students, and I don’t
> think it costs my students much sleep. (Honestly, pixel-level whizzy
> scrolling would be a much bigger deal for them.)
> >>>
> >>> John
> >>>
> >>> (obconfusion explanation: When you say “showing everything colored,”
> I’m not sure whether you mean (a) everything colored as it currently is,
> (b) everything in orange with black highlighting, or (c) everything in
> black.)
> 
> >>>
>  Robby
> 
> 
>  On Mon, Feb 15, 2016 at 3:06 PM, 'John Clements' via Racket Users
>  > wrote:
> >>
> >> I think that by the time they work hard to cover everything and the
> >> coverage colors disappear they quickly jump to a conclusion that
> >> something is wrong.  -- I even have the server report to them about
> >> uncovered code, but even that doesn't help.
> >>
> >> In case it wasn't clear -- this is not too important, just something
> >> that strikes me as weird every time another student gets confused.
> >
> > +1 to all of the above. I generally have to explain this to four or
> five students in each class.
> >
> > What if a one-line message appeared in the interactions window, just
> after the version information?
> >
> > John
> >
> >
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "Racket Users" group.
> > To unsubscribe from this group and stop receiving emails from it,
> send an email to racket-users+unsubscr...@googlegroups.com .
> > For more options, visit https://groups.google.com/d/optout.
> 
>  --
>  You received this message because you are subscribed to the Google
> Groups "Racket Users" group.
>  To unsubscribe from this group and stop receiving emails from it,
> send an email to racket-users+unsubscr...@googlegroups.com .
>  For more options, visit https://groups.google.com/d/optout.
> >>>
> >>>
> >>>
> >>> --
> >>> You received this message because you are subscribed to the Google
> Groups "Racket Users" group.
> >>> To unsubscribe from this group and stop receiving emails from it, send
> an email to racket-users+unsubscr...@googlegroups.com .
> >>> For more options, visit https://groups.google.com/d/optout.
> >
> >
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "Racket Users" group.
> > To unsubscribe 

Re: [racket-users] DrRacket Coverage

[Robby Findler]

I feel like a bar in the drracket window is a better choice than a
printout in the REPL and I've half implemented it, but it feels like
the message is a bit too far away. What do you think of these
screenshots?

http://www.eecs.northwestern.edu/~robby/tmp/a.png

http://www.eecs.northwestern.edu/~robby/tmp/b.png

Is the bar on the bottom too subtle?

Robby

On Mon, Feb 15, 2016 at 4:05 PM, 'John Clements' via Racket Users
 wrote:
>
>> On Feb 15, 2016, at 2:00 PM, Robby Findler  
>> wrote:
>>
>> I mean (c). I think (b) means "nothing ran" (right?). And I'm asking
>> if (c) is preferable to adding a "congrats!" note to the current
>> behavior.
>>
>> And I'm asking this as two questions, one about "the racket language"
>> and one about the HtDP languages.
>
> In my mind, (c) (all black) looks slightly un-festive and punitive. That may 
> just be because I’ve thoroughly internalized the current scheme, though. I 
> think I would apply this change to both the HtDP languages and the “the 
> racket language” language, though I think the case is stronger for the HtDP 
> languages (in that they are used more often by students who have a harder 
> time figuring things like this out).
>
> John
>
>>
>> Robby
>>
>> On Mon, Feb 15, 2016 at 3:50 PM, 'John Clements' via Racket Users
>>  wrote:
>>>
 On Feb 15, 2016, at 1:24 PM, Robby Findler  
 wrote:

 Do you also prefer that to just showing everything colored?
>>>
>>> To make sure I understand you (or the reverse); I’m suggesting that for a 
>>> correctly covered program, the resulting program would be colored in the 
>>> same way that it currently is for a correctly colored program (which AFAICT 
>>> is the same as the coloring before the program is run), and that a line 
>>> would be added to the interactions window. This seems like it would be less 
>>> work and less potentially irritating than a recurring (albeit disable-able) 
>>> dialog, though of course by the same token it probably makes it somewhat 
>>> more likely that students will miss it.
>>>
>>> Once again, this is not a major problem for my students, and I don’t think 
>>> it costs my students much sleep. (Honestly, pixel-level whizzy scrolling 
>>> would be a much bigger deal for them.)
>>>
>>> John
>>>
>>> (obconfusion explanation: When you say “showing everything colored,” I’m 
>>> not sure whether you mean (a) everything colored as it currently is, (b) 
>>> everything in orange with black highlighting, or (c) everything in black.)

>>>
 Robby


 On Mon, Feb 15, 2016 at 3:06 PM, 'John Clements' via Racket Users
  wrote:
>>
>> I think that by the time they work hard to cover everything and the
>> coverage colors disappear they quickly jump to a conclusion that
>> something is wrong.  -- I even have the server report to them about
>> uncovered code, but even that doesn't help.
>>
>> In case it wasn't clear -- this is not too important, just something
>> that strikes me as weird every time another student gets confused.
>
> +1 to all of the above. I generally have to explain this to four or five 
> students in each class.
>
> What if a one-line message appeared in the interactions window, just 
> after the version information?
>
> John
>
>
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Racket Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to racket-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

 --
 You received this message because you are subscribed to the Google Groups 
 "Racket Users" group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to racket-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.
>>>
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups 
>>> "Racket Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to racket-users+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Racket Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to racket-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit 

Re: [racket-users] DrRacket Coverage

['John Clements' via Racket Users]

> On Feb 15, 2016, at 2:00 PM, Robby Findler  
> wrote:
> 
> I mean (c). I think (b) means "nothing ran" (right?). And I'm asking
> if (c) is preferable to adding a "congrats!" note to the current
> behavior.
> 
> And I'm asking this as two questions, one about "the racket language"
> and one about the HtDP languages.

In my mind, (c) (all black) looks slightly un-festive and punitive. That may 
just be because I’ve thoroughly internalized the current scheme, though. I 
think I would apply this change to both the HtDP languages and the “the racket 
language” language, though I think the case is stronger for the HtDP languages 
(in that they are used more often by students who have a harder time figuring 
things like this out).

John

> 
> Robby
> 
> On Mon, Feb 15, 2016 at 3:50 PM, 'John Clements' via Racket Users
>  wrote:
>> 
>>> On Feb 15, 2016, at 1:24 PM, Robby Findler  
>>> wrote:
>>> 
>>> Do you also prefer that to just showing everything colored?
>> 
>> To make sure I understand you (or the reverse); I’m suggesting that for a 
>> correctly covered program, the resulting program would be colored in the 
>> same way that it currently is for a correctly colored program (which AFAICT 
>> is the same as the coloring before the program is run), and that a line 
>> would be added to the interactions window. This seems like it would be less 
>> work and less potentially irritating than a recurring (albeit disable-able) 
>> dialog, though of course by the same token it probably makes it somewhat 
>> more likely that students will miss it.
>> 
>> Once again, this is not a major problem for my students, and I don’t think 
>> it costs my students much sleep. (Honestly, pixel-level whizzy scrolling 
>> would be a much bigger deal for them.)
>> 
>> John
>> 
>> (obconfusion explanation: When you say “showing everything colored,” I’m not 
>> sure whether you mean (a) everything colored as it currently is, (b) 
>> everything in orange with black highlighting, or (c) everything in black.)
>>> 
>> 
>>> Robby
>>> 
>>> 
>>> On Mon, Feb 15, 2016 at 3:06 PM, 'John Clements' via Racket Users
>>>  wrote:
> 
> I think that by the time they work hard to cover everything and the
> coverage colors disappear they quickly jump to a conclusion that
> something is wrong.  -- I even have the server report to them about
> uncovered code, but even that doesn't help.
> 
> In case it wasn't clear -- this is not too important, just something
> that strikes me as weird every time another student gets confused.
 
 +1 to all of the above. I generally have to explain this to four or five 
 students in each class.
 
 What if a one-line message appeared in the interactions window, just after 
 the version information?
 
 John
 
 
 
 --
 You received this message because you are subscribed to the Google Groups 
 "Racket Users" group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to racket-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.
>>> 
>>> --
>>> You received this message because you are subscribed to the Google Groups 
>>> "Racket Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to racket-users+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>> 
>> 
>> 
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "Racket Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to racket-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.



-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [racket-users] DrRacket Coverage

[Jens Axel Søgaard]

2016-02-14 19:09 GMT+01:00 Eli Barzilay :

> Every semester there are always students that think that DrRacket is
> broken when they add tests and the coverage colors go away.  I now tell
> them about it in advance (in class and in text), but it's still
> confusing people.
>
> So in the spirit of phone apps which teach you about themselves, how
> about something like a dialog popping up when coverage is enabled, and
> there is a non-trivial program, and there's complete coverage.
> Something like a short explanation of how the colors are the same since
> your code is completely covered, with a "got it" button to dismiss it.
>

How about displaying a legend in the form of an overlay in the right upper
corner.
I am thinking something like the blue documentation overlay.

/Jens Axel

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [racket-users] DrRacket Coverage

[Robby Findler]

I mean (c). I think (b) means "nothing ran" (right?). And I'm asking
if (c) is preferable to adding a "congrats!" note to the current
behavior.

And I'm asking this as two questions, one about "the racket language"
and one about the HtDP languages.

Robby

On Mon, Feb 15, 2016 at 3:50 PM, 'John Clements' via Racket Users
 wrote:
>
>> On Feb 15, 2016, at 1:24 PM, Robby Findler  
>> wrote:
>>
>> Do you also prefer that to just showing everything colored?
>
> To make sure I understand you (or the reverse); I’m suggesting that for a 
> correctly covered program, the resulting program would be colored in the same 
> way that it currently is for a correctly colored program (which AFAICT is the 
> same as the coloring before the program is run), and that a line would be 
> added to the interactions window. This seems like it would be less work and 
> less potentially irritating than a recurring (albeit disable-able) dialog, 
> though of course by the same token it probably makes it somewhat more likely 
> that students will miss it.
>
> Once again, this is not a major problem for my students, and I don’t think it 
> costs my students much sleep. (Honestly, pixel-level whizzy scrolling would 
> be a much bigger deal for them.)
>
> John
>
> (obconfusion explanation: When you say “showing everything colored,” I’m not 
> sure whether you mean (a) everything colored as it currently is, (b) 
> everything in orange with black highlighting, or (c) everything in black.)
>>
>
>> Robby
>>
>>
>> On Mon, Feb 15, 2016 at 3:06 PM, 'John Clements' via Racket Users
>>  wrote:

 I think that by the time they work hard to cover everything and the
 coverage colors disappear they quickly jump to a conclusion that
 something is wrong.  -- I even have the server report to them about
 uncovered code, but even that doesn't help.

 In case it wasn't clear -- this is not too important, just something
 that strikes me as weird every time another student gets confused.
>>>
>>> +1 to all of the above. I generally have to explain this to four or five 
>>> students in each class.
>>>
>>> What if a one-line message appeared in the interactions window, just after 
>>> the version information?
>>>
>>> John
>>>
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups 
>>> "Racket Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to racket-users+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "Racket Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to racket-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Racket Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to racket-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [racket-users] DrRacket Coverage

['John Clements' via Racket Users]

> On Feb 15, 2016, at 1:24 PM, Robby Findler  
> wrote:
> 
> Do you also prefer that to just showing everything colored?

To make sure I understand you (or the reverse); I’m suggesting that for a 
correctly covered program, the resulting program would be colored in the same 
way that it currently is for a correctly colored program (which AFAICT is the 
same as the coloring before the program is run), and that a line would be added 
to the interactions window. This seems like it would be less work and less 
potentially irritating than a recurring (albeit disable-able) dialog, though of 
course by the same token it probably makes it somewhat more likely that 
students will miss it.

Once again, this is not a major problem for my students, and I don’t think it 
costs my students much sleep. (Honestly, pixel-level whizzy scrolling would be 
a much bigger deal for them.)

John

(obconfusion explanation: When you say “showing everything colored,” I’m not 
sure whether you mean (a) everything colored as it currently is, (b) everything 
in orange with black highlighting, or (c) everything in black.)
> 

> Robby
> 
> 
> On Mon, Feb 15, 2016 at 3:06 PM, 'John Clements' via Racket Users
>  wrote:
>>> 
>>> I think that by the time they work hard to cover everything and the
>>> coverage colors disappear they quickly jump to a conclusion that
>>> something is wrong.  -- I even have the server report to them about
>>> uncovered code, but even that doesn't help.
>>> 
>>> In case it wasn't clear -- this is not too important, just something
>>> that strikes me as weird every time another student gets confused.
>> 
>> +1 to all of the above. I generally have to explain this to four or five 
>> students in each class.
>> 
>> What if a one-line message appeared in the interactions window, just after 
>> the version information?
>> 
>> John
>> 
>> 
>> 
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "Racket Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to racket-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Racket Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to racket-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [racket-users] DrRacket Coverage

[Robby Findler]

Do you also prefer that to just showing everything colored?

Robby


On Mon, Feb 15, 2016 at 3:06 PM, 'John Clements' via Racket Users
 wrote:
>>
>> I think that by the time they work hard to cover everything and the
>> coverage colors disappear they quickly jump to a conclusion that
>> something is wrong.  -- I even have the server report to them about
>> uncovered code, but even that doesn't help.
>>
>> In case it wasn't clear -- this is not too important, just something
>> that strikes me as weird every time another student gets confused.
>
> +1 to all of the above. I generally have to explain this to four or five 
> students in each class.
>
> What if a one-line message appeared in the interactions window, just after 
> the version information?
>
> John
>
>
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Racket Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to racket-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [racket-users] DrRacket Coverage

['John Clements' via Racket Users]

> 
> I think that by the time they work hard to cover everything and the
> coverage colors disappear they quickly jump to a conclusion that
> something is wrong.  -- I even have the server report to them about
> uncovered code, but even that doesn't help.
> 
> In case it wasn't clear -- this is not too important, just something
> that strikes me as weird every time another student gets confused.

+1 to all of the above. I generally have to explain this to four or five 
students in each class. 

What if a one-line message appeared in the interactions window, just after the 
version information?

John



-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [racket-users] DrRacket Coverage

[Gustavo Massaccesi]

I guess painting everything black is more confusing, because black is
used to mark the uncovered parts. The students will think that
everything is wrong.

I think that a better possibility is to add a backcolor (and
forecolor) to the code covered by the test. I vote for very light
green,  #C0FFC0, because green usually means ok. So each time they add
more test, they will get more green background until everything is
green.

Gustavo

On Sun, Feb 14, 2016 at 7:25 PM, Robby Findler
 wrote:
> Since in that context test coverage is an opt-in kind of a thing,
> maybe it makes sense to just make the whole thing turn black? Do you
> think that would also solve the problem?
>
> Robby
>
>
> On Sun, Feb 14, 2016 at 4:10 PM, Eli Barzilay  wrote:
>> On Sun, Feb 14, 2016 at 5:06 PM, Robby Findler
>>  wrote:
>>> Can you explain the use case a little bit more, please? This is the
>>> *SL languages?
>>
>> No, a plain #lang with the syntactic code coverage enabled.
>>
>>
>>> They run their program, they see black/orange, they add tests, they no
>>> longer see black/orange, and they are confused?
>>
>> Yes exactly -- and that's after I mention it in class and describe it in
>> the course pages.
>>
>>
>>> Did they not understand what black/orange means or were they expecting
>>> entirely black?
>>
>> I think that by the time they work hard to cover everything and the
>> coverage colors disappear they quickly jump to a conclusion that
>> something is wrong.  -- I even have the server report to them about
>> uncovered code, but even that doesn't help.
>>
>> In case it wasn't clear -- this is not too important, just something
>> that strikes me as weird every time another student gets confused.
>>
>> --
>> ((x=>x(x))(x=>x(x)))   Eli Barzilay:
>> http://barzilay.org/   Maze is Life!
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Racket Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to racket-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [racket-users] DrRacket Coverage

[Robby Findler]

Can you explain the use case a little bit more, please? This is the
*SL languages? They run their program, they see black/orange, they add
tests, they no longer see black/orange, and they are confused? Did
they not understand what black/orange means or were they expecting
entirely black?

Robby


On Sun, Feb 14, 2016 at 12:09 PM, Eli Barzilay  wrote:
> Every semester there are always students that think that DrRacket is
> broken when they add tests and the coverage colors go away.  I now tell
> them about it in advance (in class and in text), but it's still
> confusing people.
>
> So in the spirit of phone apps which teach you about themselves, how
> about something like a dialog popping up when coverage is enabled, and
> there is a non-trivial program, and there's complete coverage.
> Something like a short explanation of how the colors are the same since
> your code is completely covered, with a "got it" button to dismiss it.
>
> --
> ((x=>x(x))(x=>x(x)))   Eli Barzilay:
> http://barzilay.org/   Maze is Life!
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Racket Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to racket-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [racket-users] DrRacket Coverage

[Robby Findler]

Since in that context test coverage is an opt-in kind of a thing,
maybe it makes sense to just make the whole thing turn black? Do you
think that would also solve the problem?

Robby


On Sun, Feb 14, 2016 at 4:10 PM, Eli Barzilay  wrote:
> On Sun, Feb 14, 2016 at 5:06 PM, Robby Findler
>  wrote:
>> Can you explain the use case a little bit more, please? This is the
>> *SL languages?
>
> No, a plain #lang with the syntactic code coverage enabled.
>
>
>> They run their program, they see black/orange, they add tests, they no
>> longer see black/orange, and they are confused?
>
> Yes exactly -- and that's after I mention it in class and describe it in
> the course pages.
>
>
>> Did they not understand what black/orange means or were they expecting
>> entirely black?
>
> I think that by the time they work hard to cover everything and the
> coverage colors disappear they quickly jump to a conclusion that
> something is wrong.  -- I even have the server report to them about
> uncovered code, but even that doesn't help.
>
> In case it wasn't clear -- this is not too important, just something
> that strikes me as weird every time another student gets confused.
>
> --
> ((x=>x(x))(x=>x(x)))   Eli Barzilay:
> http://barzilay.org/   Maze is Life!

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [racket-users] DrRacket Coverage

[Eli Barzilay]

On Sun, Feb 14, 2016 at 5:06 PM, Robby Findler
 wrote:
> Can you explain the use case a little bit more, please? This is the
> *SL languages?

No, a plain #lang with the syntactic code coverage enabled.


> They run their program, they see black/orange, they add tests, they no
> longer see black/orange, and they are confused?

Yes exactly -- and that's after I mention it in class and describe it in
the course pages.


> Did they not understand what black/orange means or were they expecting
> entirely black?

I think that by the time they work hard to cover everything and the
coverage colors disappear they quickly jump to a conclusion that
something is wrong.  -- I even have the server report to them about
uncovered code, but even that doesn't help.

In case it wasn't clear -- this is not too important, just something
that strikes me as weird every time another student gets confused.

-- 
((x=>x(x))(x=>x(x)))   Eli Barzilay:
http://barzilay.org/   Maze is Life!

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[racket-users] DrRacket Coverage

[Eli Barzilay]

Every semester there are always students that think that DrRacket is
broken when they add tests and the coverage colors go away.  I now tell
them about it in advance (in class and in text), but it's still
confusing people.

So in the spirit of phone apps which teach you about themselves, how
about something like a dialog popping up when coverage is enabled, and
there is a non-trivial program, and there's complete coverage.
Something like a short explanation of how the colors are the same since
your code is completely covered, with a "got it" button to dismiss it.

-- 
((x=>x(x))(x=>x(x)))   Eli Barzilay:
http://barzilay.org/   Maze is Life!

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.