[R-pkg-devel] how to skip tests on CRAN but NOT on travis-ci?

[Zhian Kamvar]

I don't know if this is the best way to do it, but I've been using the covr package (https://github.com/jimhester/covr) to run all of my tests on codecov.io even when I use testthat::skip_on_cran(). The only downside is that it increases the amount of time needed for the package to build.

HTH,
Zhian

> On Jun 21, 2015, at 07:46 , Jennifer Bryan <jenny at stat.ubc.ca> wrote:
> 
> I hope this is an appropriate to place to ask this. My question involves add-on tools and services, but I think they are in common use and others might have same question.
> 
> I am using testthat for testing and Travis (https://travis-ci.org) for continuous integration.
> 
> I do not want the vast majority of my tests to run on CRAN. They take a long time, require an internet connection, etc. I believe the official testthat solution for this is to use testthat::skip_on_cran() at the beginning of the body of the test.
> 
> However, I DO want these tests to run on Travis. In fact, I'd like to be as crazy strict on Travis as possible. More strict than on CRAN. So running R CMD check on Travis "as CRAN" is no good for me.
> 
> I think this coincides with this unanswered question on stackoverflow:
> http://stackoverflow.com/questions/27557150/check-as-cran-but-do-not-skip-any-tests?lq=1
> 
> Thanks for any suggestions,
> Jenny
> 
> Jennifer Bryan
> Associate Professor
> Department of Statistics and
>   the Michael Smith Laboratories
> University of British Columbia
> Vancouver, BC Canada
> 
> ______________________________________________
> R-package-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-package-devel