Hello everyone,
Thank you very much for your help with this! These are some excellent
ideas; I think we will go with either the mocking approach or a variant of
Dirk's suggestion to use a test threshold.
Thanks again!
Will
---
Need a phylogeny? Try phyloGenerator: original
5.4 In the spirit of simple & stupid you can also use the built in
mechanism for doing this: organize some of your tests in subdirectories
like inst/testWithInternet, inst/veryLongTests,
inst/testsNeedingLicence, inst/testsNeedingSpecialCluster, etc. CRAN
will only run the tests in the tests/
On Tue, 16 Apr 2019 at 19:57, Will wrote:
>
> Hello everyone,
>
> I'm sorry to bother you, but I would like some help getting a package (
> *suppdata*; https://github.com/ropensci/suppdata) available through CRAN.
> The package downloads supplementary materials from papers and data
> repositories
On 16 April 2019 at 11:40, Will wrote:
| Some things I have considered include:
|
|1. Skipping all unit tests on CRAN (using something like
|*testtht::skip_on_cran*). This would immediately fix the problem, and as
|a mitigating factor we report automated test result and coverage on
I'd mock the tests you want run on Cran and keep live fire tests that you
can run manually. Just don't include the live fire stuff in the package.
On Tue, Apr 16, 2019, 10:57 AM Will wrote:
> Hello everyone,
>
> I'm sorry to bother you, but I would like some help getting a package (
>
