Re: [Schematics-users] SchemeUnit redevelopment

[Gordon W. <gwe...@od...>]

How would allowing assertions to capture arbitrary failure info break compatibility with 1.x?  The way I read "break compatibility" means all tests written to 1.x would need to be fixed.  Or does it just break custom assertions? 
  
require/expose sounds awesome.  
  
I wasn't aware there was a gui, I'll try to have a look and see what it's about.  When you say drop the GUI and later redevelop it, I'm a little confused by the plan for the GUI, do you want to drop it or rewrite it? 
  
-- 
Gordon Weakliem 
http://www.eighty-twenty.net 
  
  
-----Original Message from Noel Welsh <noe...@ya...>-----
  
Development on SchemeUnit has been idle for a while and in 
that time many improvements have been suggested and some 
bit-rot has set it.  I'm resuming development of SchemeUnit 
and seeking feedback from the user community to guide the 
next version. 

My preliminary list of changes is below.  It is likely it 
will take several versions to complete this list and some 
of 
the changes with break compatability with the 1.x series. 
To avoid excessive noise I'm asking everyone who is 
interested in the future development of SchemeUnit to join 
schematics-development, if interested in guiding the 
developing, schematics-users if you merely want to stay 
abreast of the latest developments.  To sign up to either 
list visit: 

  http://sourceforge.net/mail/?group_id=19879 

Thanks, 
Noel 

SchemeUnit Proposed Changes: 

2.0 
   
  [DONE] Allow assertions to record arbitrary information 
about 
  failure.  This has already been implemented in 2.0 alpha 
  1.  Breaks compatability with 1.x 

  Add setup and teardown actions for test-suites.  Maybe 
via 
  keyword arguments.  May break compatability with 1.x 

  Drop support for GUI unless someone is willing to help 
  develop it. 

  Release as PlaneT modules in addition to Schematics 
  website 

  Add require/expose macro, aka glassbox testing. (I've 
lost 
  the source to this, if you have it please send it to me) 

  If possible improve text-ui to display backtraces 

  Miscellaneous additional assertions: 
  - assert-regexp-match 
  - assert-not-false 

  Miscellaneous additional macros: 
  - (make-test-suite* suite-name (case-name case-body) ...) 

    to reduce typing for the common case of 

    (make-test-suite 
     suite-name 
     (make-test-case 
      case-name-0 
      case-body-0) 
     (make-test-case 
      case-name-1 
      case-body-1)) 


2.1 

  Port to SISC, Scheme48 and maybe R5RS. 


2.2 

  Implement fold-tds, ala SSAX, for test-suites.  This will 
  allow more flexible traversal of test suites, and in turn 
  more flexible reporting options 

  Provide more flexible reporting options: 
  - timing information 
  - log to disk 


2.? 

  Additional add-on libraries: 
  - web testing (I have an existing incomplete framework) 
  - WebIt! (ditto) 
  - user contributions 

  Redevelop GUI and/or integrate w/ PLT's tool 

===== 
Email: noelwelsh <at> yahoo <dot> com 
AIM: noelhwelsh 

__________________________________________________ 
Do You Yahoo!? 
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


------------------------------------------------------- 
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. 
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 
_______________________________________________ 
Schematics-users mailing list 
Sch...@li... 
https://lists.sourceforge.net/lists/listinfo/schematics-users