[Bioc-devel] "extra" unit tests

Levi Waldron lwaldron.research at gmail.com
Wed Oct 25 05:21:28 CEST 2017

Thanks Pete! Didn't know about those.

On Oct 24, 2017 11:17 PM, "Peter Hickey" <peter.hickey at gmail.com> wrote:

> A partial answer if you are using the 'testthat' framework: you can use
> `testthat::skip_on_bioc()` to specify that a test should be skipped if it
> is running on the BioC build machines. The test will otherwise be run
> (e.g., during local development). There are some other `testthat::skip*()`
> functions that may also be useful.
> Cheers,
> Pete
> On Wed, 25 Oct 2017 at 12:47 Levi Waldron <lwaldron.research at gmail.com>
> wrote:
>> Any thoughts about how to implement optional or "extra" unit tests, that
>> are too resource intensive to be part of the Bioconductor daily builds,
>> but
>> that should be run once in a while, say with major updates?
>>         [[alternative HTML version deleted]]
>> _______________________________________________
>> Bioc-devel at r-project.org mailing list
>> https://stat.ethz.ch/mailman/listinfo/bioc-devel

	[[alternative HTML version deleted]]

More information about the Bioc-devel mailing list