roxut: Document Unit Tests Roxygen-Style

Much as 'roxygen2' allows one to document functions in the same file as the function itself, 'roxut' allows one to write the unit tests in the same file as the function. Once processed, the unit tests are moved to the appropriate directory. Currently supports 'testthat' and 'tinytest' frameworks. The 'roxygen2' package provides much of the infrastructure.

Version: 0.2.23
Depends: roxygen2 (≥ 7.1)
Suggests: tinytest, testthat
Published: 2020-07-06
Author: Bryan A. Hanson ORCID iD [aut, cre], Hadley Wickham [aut, cph] (roxygen2 code), Peter Danenberg [aut, cph] (roxygen2 code), Gábor Csárdi [aut] (roxygen2 code), Manuel Eugster [aut, cph] (roxygen2 code), RStudio [cph] (roxygen2 code)
Maintainer: Bryan A. Hanson <hanson at depauw.edu>
BugReports: https://github.com/bryanhanson/roxut/issues
License: GPL-3
URL: https://github.com/bryanhanson/roxut
NeedsCompilation: no
Materials: NEWS
CRAN checks: roxut results

Downloads:

Reference manual: roxut.pdf
Package source: roxut_0.2.23.tar.gz
Windows binaries: r-devel: roxut_0.2.23.zip, r-release: roxut_0.2.23.zip, r-oldrel: roxut_0.2.23.zip
macOS binaries: r-release: roxut_0.2.23.tgz, r-oldrel: roxut_0.2.23.tgz

Reverse dependencies:

Reverse suggests: ChemoSpecUtils

Linking:

Please use the canonical form https://CRAN.R-project.org/package=roxut to link to this page.