Fixing sloppy rename. Include in release.

collects/rackunit/info.rkt

@@ -1,13 +1,13 @@
 #lang setup/infotab
 
-(define name "RacUnit")
+(define name "RackUnit")
 
-(define blurb '((p "RacUnit is a unit testing framework based on the "
+(define blurb '((p "RackUnit is a unit testing framework based on the "
                    " Extreme Programming unit test frameworks")))
 
 (define scribblings '(("scribblings/rackunit.scrbl" (multi-page) (tool))))
 (define tools '[("tool.rkt")])
-(define tool-names '["RacUnit DrRacket integration"])
+(define tool-names '["RackUnit DrRacket integration"])
 
 (define homepage "http://schematics.sourceforge.net/")
 (define url "http://schematics.sourceforge.net/")

collects/rackunit/private/gui/config.rkt

@@ -14,11 +14,11 @@
 ;; Some of these are obsolete, given the preferences above.
 
 (define DETAILS-CANVAS-INIT-WIDTH 400)
-(define FRAME-LABEL "RacUnit")
+(define FRAME-LABEL "RackUnit")
 (define FRAME-INIT-HEIGHT 400)
 (define TREE-INIT-WIDTH 240)
 (define TREE-COLORIZE-CASES #t)
-(define DIALOG-ERROR-TITLE "RacUnit: Error")
+(define DIALOG-ERROR-TITLE "RackUnit: Error")
 (define STATUS-SUCCESS 'success)
 (define STATUS-FAILURE 'failure)
 (define STATUS-ERROR 'error)

collects/rackunit/private/gui/controller.rkt

@@ -25,9 +25,9 @@
     ;; check-ready : -> void
     (define/private (check-ready)
       (unless view
-        (error 'racunit "The RacUnit GUI is no longer running."))
+        (error 'racunit "The RackUnit GUI is no longer running."))
       (when (get-locked?)
-        (error 'racunit "The RacUnit GUI is locked and not accepting tests.")))
+        (error 'racunit "The RackUnit GUI is locked and not accepting tests.")))
 
     ;; create-model : test suite<%>/#f -> result<%>
     (define/public (create-model test parent)

collects/rackunit/private/gui/view.rkt

@@ -308,11 +308,11 @@ still be there, just not visible?
 
     (super-new (width width) (height height))
     (send (get-help-menu) delete)
-    (let ([racunit-menu
+    (let ([rackunit-menu
            (new menu%
-                (label "RacUnit")
+                (label "RackUnit")
                 (parent (get-menu-bar)))])
-      (menu-option/notify-box racunit-menu
+      (menu-option/notify-box rackunit-menu
                               "Lock"
                               (get-field locked? controller)))
 

collects/rackunit/scribblings/acknowledgements.scrbl

@@ -3,7 +3,7 @@
 
 @title{Acknowlegements}
 
-The following people have contributed to RacUnit:
+The following people have contributed to RackUnit:
 
 @itemize[
   @item{Robby Findler pushed me to release version 3}
@@ -12,7 +12,7 @@ The following people have contributed to RacUnit:
   suggested renaming @racket[test/text-ui]}
 
   @item{Dave Gurnell reported a bug in check-not-exn and
-  suggested improvements to RacUnit}
+  suggested improvements to RackUnit}
 
   @item{Danny Yoo reported a bug in and provided a fix for
     trim-current-directory}
@@ -30,7 +30,7 @@ The following people have contributed to RacUnit:
   @item{Jose A. Ortega Ruiz alerted me a problem in the
     packaging system and helped fix it.}
 
-  @item{Sebastian H. Seidel provided help packaging RacUnit
+  @item{Sebastian H. Seidel provided help packaging RackUnit
     into a .plt}
 
   @item{Don Blaheta provided the method for grabbing line number

collects/rackunit/scribblings/api.scrbl

@@ -1,7 +1,7 @@
 #lang scribble/doc
 @(require "base.rkt")
 
-@title[#:tag "api"]{RacUnit API}
+@title[#:tag "api"]{RackUnit API}
 
 @defmodule[rackunit
   #:use-sources (rackunit)]

collects/rackunit/scribblings/check.scrbl

@@ -3,7 +3,7 @@
 
 @title{Checks}
 
-Checks are the basic building block of RacUnit.  A check
+Checks are the basic building block of RackUnit.  A check
 checks some condition.  If the condition holds the check
 evaluates to @racket[#t].  If the condition doesn't hold the
 check raises an instance of @racket[exn:test:check] with
@@ -16,7 +16,7 @@ their arguments.  You can use check as first class
 functions, though you will lose precision in the reported
 source locations if you do so.
 
-The following are the basic checks RacUnit provides.  You
+The following are the basic checks RackUnit provides.  You
 can create your own checks using @racket[define-check].
 
 @defproc[(check (op (-> any any any))

collects/rackunit/scribblings/compound-testing.scrbl

@@ -147,7 +147,7 @@ creates test cases within the suite, with the given names and
 body expressions.
 
 As far I know no-one uses this macro, so it might disappear
-in future versions of RacUnit.}
+in future versions of RackUnit.}
 }
 
 

collects/rackunit/scribblings/control-flow.scrbl

@@ -48,5 +48,5 @@ file.  The after action deletes it.
 This somewhat curious macro evaluates the given tests in a
 context where @racket[current-test-case-around] is
 parameterized to @racket[test-suite-test-case-around].  This
-has been useful in testing RacUnit.  It might be useful
+has been useful in testing RackUnit.  It might be useful
 for you if you create test cases that create test cases.}

collects/rackunit/scribblings/misc.scrbl

@@ -14,7 +14,7 @@ Note that @racket[require/expose] can be a bit fragile,
 especially when mixed with compiled code.  Use at your own risk!
 }
 
-This example gets @racket[make-failure-test], which is defined in a RacUnit test:
+This example gets @racket[make-failure-test], which is defined in a RackUnit test:
 
 @racketblock[
 (require/expose rackunit/private/check-test (make-failure-test))

collects/rackunit/scribblings/overview.scrbl

@@ -1,9 +1,9 @@
 #lang scribble/doc
 @(require "base.rkt")
 
-@title{Overview of RacUnit}
+@title{Overview of RackUnit}
 
-There are three basic data types in RacUnit:
+There are three basic data types in RackUnit:
 
 @itemize[
 

collects/rackunit/scribblings/philosophy.scrbl

@@ -1,10 +1,10 @@
 #lang scribble/doc
 @(require "base.rkt")
 
-@title[#:tag "philosophy"]{The Philosophy of RacUnit}
+@title[#:tag "philosophy"]{The Philosophy of RackUnit}
 
-RacUnit is designed to allow tests to evolve in step with
-the evolution of the program under testing.  RacUnit
+RackUnit is designed to allow tests to evolve in step with
+the evolution of the program under testing.  RackUnit
 scales from the unstructed checks suitable for simple
 programs to the complex structure necessary for large
 projects.
@@ -25,9 +25,9 @@ checking are of the form:
   (equal? (length '(a b)) 2)
 ]
 
-RacUnit directly supports this style of testing.  A check
+RackUnit directly supports this style of testing.  A check
 on its own is a valid test.  So the above examples may be
-written in RacUnit as:
+written in RackUnit as:
 
 @racketblock[
   (check-equal? (length null) 0)
@@ -35,7 +35,7 @@ written in RacUnit as:
   (check-equal? (length '(a b)) 2)
 ]
 
-Simple programs now get all the benefits of RacUnit with
+Simple programs now get all the benefits of RackUnit with
 very little overhead.
 
 There are limitations to this style of testing that more
@@ -45,7 +45,7 @@ it does not make sense to evaluate some expressions if
 earlier ones have failed.  This type of program needs a way
 to group expressions so that a failure in one group causes
 evaluation of that group to stop and immediately proceed to
-the next group.  In RacUnit all that is required is to
+the next group.  In RackUnit all that is required is to
 wrap a @racket[test-begin] expression around a group of
 expressions:
 
@@ -62,7 +62,7 @@ be evaluated.
 
 Notice that all the previous tests written in the simple
 style are still valid.  Introducing grouping is a local
-change only.  This is a key feature of RacUnit's support
+change only.  This is a key feature of RackUnit's support
 for the evolution of the program.
 
 The programmer may wish to name a group of tests.  This is
@@ -79,7 +79,7 @@ Most programs will stick with this style. However,
 programmers writing very complex programs may wish to
 maintain separate groups of tests for different parts of the
 program, or run their tests in different ways to the normal
-RacUnit manner (for example, test results may be logged
+RackUnit manner (for example, test results may be logged
 for the purpose of improving software quality, or they may
 be displayed on a website to indicate service quality). For
 these programmers it is necessary to delay the execution of
@@ -104,15 +104,15 @@ outside the suite continue to evaluate as before.
 @section{Historical Context}
 
 Most testing frameworks, including earlier versions of
-RacUnit, support only the final form of testing. This is
+RackUnit, support only the final form of testing. This is
 likely due to the influence of the SUnit testing framework,
-which is the ancestor of RacUnit and the most widely used
+which is the ancestor of RackUnit 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''
 testing frameworks in Racket such as SRFI-78, or the
 practice of beginner programmers. Unfortunately these
 simpler methods are inadequate for testing larger
-systems. To the best of my knowledge RacUnit is the only
+systems. To the best of my knowledge RackUnit is the only
 testing framework that makes a conscious effort to support
 the testing style of all levels of programmer.

collects/rackunit/scribblings/quick-start.scrbl

@@ -1,7 +1,7 @@
 #lang scribble/doc
 @(require "base.rkt")
 
-@title[#:tag "quick-start"]{Quick Start Guide for RacUnit}
+@title[#:tag "quick-start"]{Quick Start Guide for RackUnit}
 
 Suppose we have code contained in @tt{file.rkt}, which
 implements buggy versions of @racket[+] and @racket[-]
@@ -24,10 +24,10 @@ racket/base
          my-*)
 ]
 
-We want to test this code with RacUnit.  We start by
+We want to test this code with RackUnit.  We start by
 creating a file called @tt{file-test.rkt} to contain our
 tests.  At the top of @tt{file-test.rkt} we import
-RacUnit and @tt{file.rkt}:
+RackUnit and @tt{file.rkt}:
 
 @racketmod[
 racket/base
@@ -43,7 +43,7 @@ Now we add some tests to check our library:
 (check-equal? (my-* 1 2) 2 "Simple multiplication")
 ]
 
-This is all it takes to define tests in RacUnit.  Now
+This is all it takes to define tests in RackUnit.  Now
 evaluate this file and see if the library is correct.
 Here's the result I get:
 
@@ -63,13 +63,13 @@ expected:   2
 The first @racket[#t] indicates the first test passed.  The
 second test failed, as shown by the message.
 
-Requiring RacUnit and writing checks is all you need to
+Requiring RackUnit and writing checks is all you need to
 get started testing, but let's take a little bit more time
 to look at some features beyond the essentials.
 
 Let's say we want to check that a number of properties hold.
 How do we do this?  So far we've only seen checks of a
-single expression.  In RacUnit a check is always a single
+single expression.  In RackUnit a check is always a single
 expression, but we can group checks into units called test
 cases.  Here's a simple test case written using the
 @racket[test-begin] form:
@@ -147,7 +147,7 @@ tests, allowing you to choose how you run your tests.  You
 might, for example, print the results to the screen or log
 them to a file.
 
-Let's run our tests, using RacUnit's simple textual user
+Let's run our tests, using RackUnit's simple textual user
 interface (there are fancier interfaces available but this
 will do for our example).  In @tt{file-test.rkt} add the
 following lines:
@@ -161,6 +161,6 @@ following lines:
 Now evaluate the file and you should see similar output
 again.
 
-These are the basics of RacUnit.  Refer to the
+These are the basics of RackUnit.  Refer to the
 documentation below for more advanced topics, such as
 defining your own checks.  Have fun!

collects/rackunit/scribblings/rackunit.scrbl

@@ -1,12 +1,12 @@
 #lang scribble/doc
 @(require "base.rkt")
 
-@title{@bold{RacUnit}: Unit Testing for Racket}
+@title{@bold{RackUnit}: Unit Testing for Racket}
 
 @author[(author+email "Noel Welsh" "noelwelsh@gmail.com")
         (author+email "Ryan Culpepper" "ryan_sml@yahoo.com")]
 
-RacUnit is a unit-testing framework for Racket.  It
+RackUnit is a unit-testing framework for Racket.  It
 is designed to handle the needs of all Racket programmers,
 from novices to experts.
 

collects/rackunit/scribblings/release-notes.scrbl

@@ -12,7 +12,7 @@ There are also miscellaneous Scribble fixes.
 
 @section{Version 3}
 
-This version of RacUnit is largely backwards compatible
+This version of RackUnit is largely backwards compatible
 with version 2 but there are significant changes to the
 underlying model, justifying incrementing the major version
 number.  These changes are best explained in

collects/rackunit/scribblings/running-tests.scrbl

@@ -3,14 +3,14 @@
 
 @title[#:tag "running"]{Programmatically Running Tests and Inspecting Results}
 
-RacUnit provides an API for running tests, from which
+RackUnit provides an API for running tests, from which
 custom UIs can be created.
 
 @section{Result Types}
 
 @defstruct[(exn:test exn) ()]{
 
-The base structure for RacUnit exceptions.  You should
+The base structure for RackUnit exceptions.  You should
 never catch instances of this type, only the subtypes
 documented below.}
 
@@ -187,7 +187,7 @@ recorded, and so on.  To do so the functions that run the
 test cases need to know what type the test case has, and
 hence is is necessary to provide this information.
 
-If you've made it this far you truly are a master RacUnit
+If you've made it this far you truly are a master RackUnit
 hacker.  As a bonus prize we'll just mention that the code
 in hash-monad.rkt and monad.rkt might be of interest for
 constructing user interfaces.  The API is still in flux, so

collects/rackunit/scribblings/ui.scrbl

@@ -3,7 +3,7 @@
 
 @title[#:tag  "ui"]{User Interfaces}
 
-RacUnit provides a textual and a graphical user interface
+RackUnit provides a textual and a graphical user interface
 
 @section{Textual User Interface}
 
@@ -35,13 +35,13 @@ information.
 
 @defmodule[rackunit/gui]
 
-RacUnit also provides a GUI test runner, available from the
+RackUnit also provides a GUI test runner, available from the
 @racketmodname[rackunit/gui] module.
 
 @defproc[(test/gui [test (or/c test-case? test-suite?)] ...)
          any]{
 
-Creates a new RacUnit GUI window and runs each @racket[test]. The
+Creates a new RackUnit GUI window and runs each @racket[test]. The
 GUI is updated as tests complete.
 
 }
@@ -49,7 +49,7 @@ GUI is updated as tests complete.
 @defproc[(make-gui-runner)
          (-> (or/c test-case? test-suite?) ... any)]{
 
-Creates a new RacUnit GUI window and returns a procedure that, when
+Creates a new RackUnit GUI window and returns a procedure that, when
 applied, runs the given tests and displays the results in the GUI.
 
 }