Fix typos

Fixes #1799

Author: hadley

NEWS.md

@@ -397,7 +397,7 @@
 * `CheckReporter` now only records warnings when not on CRAN. Otherwise 
   failed CRAN revdep checks tend to be cluttered up with warnings (#1300).
   It automatically cleans up `testthat-problems.rds` left over from previous
-  runs if the latest run is succesful (#1314).
+  runs if the latest run is successful (#1314).
 
 * `expect_s3_class()` and `expect_s4_class()` can now check that an object
   _isn't_ an S3 or S4 object by supplying `NA` to the second argument (#1321).
@@ -559,7 +559,7 @@ See `vignette("snapshotting")` for more details.
 
 * Many reporters (e.g. the check reporter) no longer raise an error when any tests fail. Use the `stop_on_failure` argument to `devtools::test()` and `testthat::test_dir()` if your code relies on this. Alternatively, use `reporter = c("check", "fail")` to e.g. create a failing check reporter.
 
-## Fixures
+## Fixtures
 
 * New `vignette("test-fixtures")` describes test fixtures; i.e. how to 
   temporarily and cleanly change global state in order to test parts of
@@ -664,7 +664,7 @@ This release mostly focusses on an overhaul of how testthat works with condition
   implements the testthat protocol (signal with `stop()` if the
   expectation is broken, with a `continue_test` restart).
 
-* Existence of restarts is first checked before invokation. This makes
+* Existence of restarts is first checked before invocation. This makes
   it possible to signal warnings or messages with a different
   condition signaller (#874).
 
@@ -835,7 +835,7 @@ This release mostly focusses on an overhaul of how testthat works with condition
 * `CheckReporter`, used by R CMD check, now includes a count of warnings.
 
 * `JUnitReporter` no longer replaces `.` in class names (#753), and
-  creates ouput that should be more compatible with Jenkins (#806, @comicfans).
+  creates output that should be more compatible with Jenkins (#806, @comicfans).
 
 * `ListReporter` now records number of passed tests and original results in 
   new columns (#675).
@@ -846,7 +846,7 @@ This release mostly focusses on an overhaul of how testthat works with condition
       recommend the use of `context()` and instead encourage you to delete it,
       allowing the context to be autogenerated from the file name.
 
-      This also eliminates the error that occured if tests can before the
+      This also eliminates the error that occurred if tests can before the
       first `context()` (#700, #705). 
 
     * Gains a `update_interval` parameter to control how often updates are 
@@ -990,7 +990,7 @@ We have identified a useful family of expectations that compares the results of
 
 * `expect_known_failure()` stored and compares the failure message from
   an expectation. It's a useful regression test when developing informative
-  failure messges for your own expectations.
+  failure messages for your own expectations.
 
 ### Quasiquotation support
 
@@ -1069,7 +1069,7 @@ A new default reporter, `ReporterProgress`, produces more aesthetically pleasing
 * New `LocationReporter` which just prints the location of every expectation.
   This is useful for locating segfaults and C/C++ breakpoints (#551).
 
-* `SummaryReporter` recieved a number of smaller tweaks
+* `SummaryReporter` received a number of smaller tweaks
 
   * Aborts testing as soon the limit given by the option 
     `testthat.summary.max_reports` (default 10) is reached (#520).
@@ -1227,7 +1227,7 @@ factor("a") %>%
 (And to make this style even easier, testthat now re-exports the pipe, #412).
 
 The exception to this rule are the expectations that evaluate (i.e.
-for messages, warnings, errors, output etc), which invisibly return `NULL`. These functions are now more consistent: using `NA` will cause a failure if there is a errors/warnings/mesages/output (i.e. they're not missing), and will `NULL` fail if there aren't any errors/warnings/mesages/output. This previously didn't work for `expect_output()` (#323), and the error messages were confusing with `expect_error(..., NA)` (#342, @nealrichardson + @krlmlr, #317).
+for messages, warnings, errors, output etc), which invisibly return `NULL`. These functions are now more consistent: using `NA` will cause a failure if there is a errors/warnings/messages/output (i.e. they're not missing), and will `NULL` fail if there aren't any errors/warnings/messages/output. This previously didn't work for `expect_output()` (#323), and the error messages were confusing with `expect_error(..., NA)` (#342, @nealrichardson + @krlmlr, #317).
 
 Another change is that `expect_output()` now requires you to explicitly print the output if you want to test a print method: `expect_output("a", "a")` will fail, `expect_output(print("a"), "a")` will succeed.
 
@@ -1362,7 +1362,7 @@ The reporters system class has been considerably refactored to make existing rep
   output, messages, warnings, and errors should be absent (#219).
 
 * Praise gets more diverse thanks to the praise package, and you'll now
-  get random encouragment if your tests don't pass.
+  get random encouragement if your tests don't pass.
 
 * testthat no longer muffles warning messages. If you don't want to see them 
   in your output, you need to explicitly quiet them, or use an expectation that 
@@ -1398,7 +1398,7 @@ The reporters system class has been considerably refactored to make existing rep
 
 # testthat 0.10.0
 
-* Failure locations are now formated as R error locations.
+* Failure locations are now formatted as R error locations.
 
 * Add an 'invert' argument to `find_tests_scripts()`.  This allows one to
   select only tests which do _not_ match a pattern. (#239, @jimhester).
@@ -1458,7 +1458,7 @@ The reporters system class has been considerably refactored to make existing rep
 ## New features
 
 * BDD: testhat now comes with an initial behaviour driven development (BDD)
-  interface. The language is similiar to RSpec for Ruby or Mocha for JavaScript.
+  interface. The language is similar to RSpec for Ruby or Mocha for JavaScript.
   BDD tests read like sentences, so they should make it easier to understand
   the specification of a function. See `?describe()` for further information
   and examples.
@@ -1523,7 +1523,7 @@ tests.
 
 The other big improvement to usability comes from @kforner, who contributed
 code to allow the default results (i.e. those produced by `SummaryReporter`)
-to include source references so you can see exactly where failures occured.
+to include source references so you can see exactly where failures occurred.
 
 ## New reporters
 

R/auto-test.R

@@ -1,7 +1,7 @@
 #' Watches code and tests for changes, rerunning tests as appropriate.
 #'
 #' The idea behind `auto_test()` is that you just leave it running while
-#' you develop your code.  Everytime you save a file it will be automatically
+#' you develop your code.  Every time you save a file it will be automatically
 #' tested and you can easily see if your changes have caused any test
 #'  failures.
 #'

R/describe.R

@@ -1,6 +1,6 @@
 #' describe: a BDD testing language
 #'
-#' A simple BDD DSL for writing tests. The language is similiar to RSpec for
+#' A simple BDD DSL for writing tests. The language is similar to RSpec for
 #' Ruby or Mocha for JavaScript. BDD tests read like sentences and it should
 #' thus be easier to understand what the specification of a function/component
 #' is.

R/mock.R

@@ -20,7 +20,7 @@
 #' @param .env the environment in which to patch the functions,
 #'   defaults to the top-level environment.  A character is interpreted as
 #'   package name.
-#' @param .local_env Environment in which to add exit hander.
+#' @param .local_env Environment in which to add exit handler.
 #'   For expert use only.
 #' @keywords internal
 #' @return The result of the last unnamed parameter

man/auto_test.Rd

@@ -1,4 +1,4 @@
-test_that("can supress colours", {
+test_that("can suppress colours", {
   op <- options(
     crayon.enabled = TRUE,
     testthat.use_colours = TRUE,

man/describe.Rd

@@ -48,7 +48,7 @@ test_that("comparison must yield a single logical", {
   expect_error(expect_lt(1:10, 5), "single logical")
 })
 
-test_that("wordly versions are deprecated", {
+test_that("wordy versions are deprecated", {
   expect_warning(expect_less_than(1, 2), "Deprecated")
   expect_warning(expect_more_than(2, 1), "Deprecated")
 })

man/with_mock.Rd

@@ -1,4 +1,4 @@
-test_that("basically principles of visibilty hold", {
+test_that("basic principles of visibility hold", {
   expect_success(expect_invisible(x <- 10))
   expect_failure(expect_invisible(x))