schemeunit doc tweaks
svn: r14269
This commit is contained in:
parent
def73634ee
commit
7aaa0ae48a
|
@ -164,7 +164,9 @@ misspelling errors:
|
|||
|
||||
@defproc*[([(make-check-name (name string?)) check-info?]
|
||||
[(make-check-params (params (listof any))) check-info?]
|
||||
[(make-check-location (loc (list any (or/c number? #f) (or/c number? #f) (or/c number? #f) (or/c number? #f)))) check-info?]
|
||||
[(make-check-location (loc (list/c any (or/c number? #f) (or/c number? #f)
|
||||
(or/c number? #f) (or/c number? #f))))
|
||||
check-info?]
|
||||
[(make-check-expression (msg any)) check-info?]
|
||||
[(make-check-message (msg string?)) check-info?]
|
||||
[(make-check-actual (param any)) check-info?]
|
||||
|
|
|
@ -109,7 +109,7 @@ likely due to the influence of the SUnit testing framework,
|
|||
which is the ancestor of SchemeUnit and the most widely used
|
||||
frameworks in Java, .Net, Python, and Ruby, and many other
|
||||
languages. That this is insufficient for all users is
|
||||
apparent if one considers the proliferation of "simpler"
|
||||
apparent if one considers the proliferation of ``simpler''
|
||||
testing frameworks in Scheme such as SRFI-78, or the the
|
||||
practice of beginner programmers. Unfortunately these
|
||||
simpler methods are inadequate for testing larger
|
||||
|
|
Loading…
Reference in New Issue
Block a user