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

[Facundo Muñoz]

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.


Cheers
        ƒacu.-