Schematics

--- Noel Welsh <noelwelsh@...> wrote:
> I've finally fixed the SchemeUnit fold bugs (finally
> grokked "A Fold for All Seasons").  I've checked in
> the mods, but didn't get time to patch all the tests. 
> The remaining breakages should be trivial to fix.  Not
> so sure about the GUI as I don't know if it has
> dependencies on the folds and it's tests don't seem to
> be integrated into the main all-schemeunit-tests.ss

I'm not using the SchemeUnit fold because of the way I wrap tests for
the GUIs. I've also been trying to minimize dependencies between the
GUI code and the core SchemeUnit code, since those dependencies must
be explicitly packaged up for the creation of a DrScheme tool.

For the GUI I've been using the file demo-interface.scm or something
like that to see how different types of tests are handled and
displayed. I've gotten to the point where I can do separate tests on
parts of the GUI, but I haven't written them. (Writing tests *for*
GUIs is something I haven't yet fully understood. Working on that.)

When are you thinking of making the next release? I've got a few more
things to tidy up or implement and commit, and then I think the GUI
code will be ready to go. I'll send a more detailed changes/todo
message when I get home where my notes are.

Ryan



__________________________________________________
Do you Yahoo!?
Y! Web Hosting - Let the expert host your web site
http://webhosting.yahoo.com/

(replying to myself)
> ...
> I'll send a more detailed changes/todo
> message when I get home where my notes are.

Recent changes include lots of internal improvements, better
organization, and two new features visible to users. There is a
teachpack that will allow SchemeUnit to be used in other DrScheme
languages (like Beginner, Essentials of Programming Languages 2,
etc). The test case entries of the tree are now colorized depending
on the result of running the test (green for success, red for
failures and errors).

I've fiddled a little bit with threads in an effort to not have the
UI hang when a test case loops forever or just takes a long time.
None of the simple answers quite worked, so after this release I
intend to invest some time figuring out the correct solution with
threads and synchronization.

I've thought of two other features that I think would be useful, and
I'd like any feedback people have. First, the ability to generate a
report (probably in HTML) from the test results would be useful. This
could probably done before the next release if people are interested
in it. Second, we might be able to leverage DrScheme's profiling
features to show code coverage of tests and flag code that is not
being tested. This would require significantly more time and effort.
If you have feelings either way about these, please let me know.

Ryan


__________________________________________________
Do you Yahoo!?
Y! Web Hosting - Let the expert host your web site
http://webhosting.yahoo.com/

--- Ryan Culpepper <ryan_sml@...> wrote:
> When are you thinking of making the next release?

Soon.  We have enough new functionality to justify a
new release.  All we need a docs.  I got ragged about
them:

http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&threadm=cdac2dde.0209060618.48b9d813%40posting.google.com&rnum=2&prev=/groups%3Fq%3Ddocumentation%2Bschemeunit%26hl%3Den%26lr%3D%26ie%3DUTF-8%26oe%3DUTF-8%26selm%3Dcdac2dde.0209060618.48b9d813%2540posting.google.com%26rnum%3D2

so I'd like to make the next version of the docs a bit
better.  The current docs are hand-crafted HTML.  I
think switching to slatex would be better.  I hate
LaTex as much as the next person but there isn't a
better solution right now.

Noel


__________________________________________________
Do you Yahoo!?
Y! Web Hosting - Let the expert host your web site
http://webhosting.yahoo.com/

--- Ryan Culpepper <ryan_sml@...> wrote:
> Recent changes include lots of internal
> improvements, better
> organization, and two new features visible to users.
> There is a
> teachpack that will allow SchemeUnit to be used in
> other DrScheme
> languages (like Beginner, Essentials of Programming
> Languages 2,
> etc).

Cool.  Mike "TMac" MacHenry is working on something
similar.  I've CC'ed him; you guys might want to
collaborate.


> None of the simple answers quite worked, so after
> this release I
> intend to invest some time figuring out the correct
> solution with
> threads and synchronization.

Good plan.
 
> First, the ability to generate a
> report (probably in HTML) from the test results
> would be useful. 

Ant?JUnit have something simliar; might be worth
looking at.  I'm interested in logging test results to
a db to see if there any interesting information that
can be extracted for project mgmt.  I.e. can tracking
tests give us an idea of how well a project is
progressing?  Probably won't show much on 1-man
projects but might yield interesting information on
bigger projects.  Plus, we mentioned doing this in the
Scheme Workshop paper ;-)

> This
> could probably done before the next release if
> people are interested
> in it.

I wouldn't rush it.  Better to get the release out.

> Second, we might be able to leverage
> DrScheme's profiling
> features to show code coverage of tests and flag
> code that is not
> being tested. 

This would be tres cool!  Oblig. JUnit reference:
Clover.

Noel

__________________________________________________
Do you Yahoo!?
Y! Web Hosting - Let the expert host your web site
http://webhosting.yahoo.com/

Noel Welsh <noelwelsh@...> wrote:
> The current docs are hand-crafted HTML.  I think switching to slatex would
> be better.  I hate LaTex as much as the next person but there isn't a
> better solution right now.

Does the code belong in the documentation (a la slatex) or does the
documentation belong in the code (a la Mole and SchemeDoc)?  If you use
slatex, can graphical editors like TeXmacs cope with it?

This problem has been exercising me lately.  Because I tend to get the
working code and then flesh out the documentation, I'm leaning towards the
Mole side of the divide, but I'm not sure.

MJR

--- MJ Ray <markj@...> wrote:
> Does the code belong in the documentation (a la
> slatex) or does the
> documentation belong in the code (a la Mole and
> SchemeDoc)?  If you use
> slatex, can graphical editors like TeXmacs cope with
> it?

I lean towards API documentation in the source code
and other documentation kept separately.  My reasoning
being that if I change the API I can change the API
documentation straight away, but having all the
documentation mixed in with the source code would
obscure things too much.  Then again, I've used
JavaDoc but I've never used a literate programming
system.

Noel

__________________________________________________
Do you Yahoo!?
HotJobs - Search new jobs daily now
http://hotjobs.yahoo.com/

--- Ryan Culpepper <ryan_sml@...> wrote:
> (Writing tests *for*
> GUIs is something I haven't yet fully understood.
> Working on that.)

It's a tough problem that I haven't solved yet.  There
are some ideas at

  http://c2.com/cgi/wiki?GuiTesting

I have a vague memory of a GUI event capture tool in
PLT Scheme but can't find a reference anywhere.

If you use a MVC architecture than you can test the M
and C independently of the GUI.  For the GUI things
like button callbacks can probably be tested
independently of the actual "draw things on the
screen" bit.

HTH,
Noel

__________________________________________________
Do you Yahoo!?
HotJobs - Search new jobs daily now
http://hotjobs.yahoo.com/