[R-pkg-devel] coercion in R CMD check

Dirk Eddelbuettel edd at debian.org
Thu Dec 3 00:35:27 CET 2015

On 3 December 2015 at 00:24, Facundo Muñoz wrote:
| I have been struggling all day with this issue, which was terribly
| difficult to identify.
| In the end, if I have a test in my package such as:
| test_that("coercions works... depending the check", {
|   s = "/A/string/starting/with/a/slash"
|   expect_true(s > 0)
| })
| then if I test() it, it goes fine.
| But if I R CMD check the packaged source, it fails.
| I don't understand the difference between the testing performed by R CMD
| check, and the testing performed by myself. It is not related with
| --as-cran.

Do have testthat loaded?  Can you analyse a minimal working package and see
what is different?  We don't have your package so ...   Start from one of the
hundreds of testthat using packages on CRAN and see what they do.


http://dirk.eddelbuettel.com | @eddelbuettel | edd at debian.org

More information about the R-package-devel mailing list