The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.
Automatic testing of R packages by tracing function calls made in examples and tests, then systematically varying the inputs to check that functions respond sensibly. The package is a development aid for authors submitting to the 'rOpenSci' statistical software review project ('rOpenSci' authors, 2021; <doi:10.5281/zenodo.5556756>).
| Version: | 0.2.0 |
| Imports: | checkmate, cli, data.table, fs, grDevices, here, magrittr, memoise, methods, pkgload, rlang, testthat, tibble, typetracer, withr |
| Suggests: | devtools, dplyr, DT, goodpractice, knitr, rmarkdown, roxygen2, tidyr, usethis |
| Published: | 2026-09-12 |
| DOI: | 10.32614/CRAN.package.autotest (may not be active yet) |
| Author: | Mark Padgham |
| Maintainer: | Mark Padgham <mark.padgham at email.com> |
| BugReports: | https://github.com/ropensci-review-tools/autotest/issues |
| License: | GPL-3 |
| URL: | https://docs.ropensci.org/autotest/, https://github.com/ropensci-review-tools/autotest |
| NeedsCompilation: | no |
| Language: | en-GB |
| Materials: | README, NEWS |
| CRAN checks: | autotest results |
| Reference manual: | autotest.html , autotest.pdf |
| Vignettes: |
Control of tests (source, R code) autotest, pkgcheck, goodpractice - which tool does what? (source, R code) How to use autotest (source, R code) |
| Package source: | autotest_0.2.0.tar.gz |
| Windows binaries: | r-devel: not available, r-release: not available, r-oldrel: not available |
| macOS binaries: | r-release (arm64): not available, r-oldrel (arm64): autotest_0.2.0.tgz, r-release (x86_64): autotest_0.2.0.tgz, r-oldrel (x86_64): autotest_0.2.0.tgz |
Please use the canonical form https://CRAN.R-project.org/package=autotest to link to this page.
These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.