[Bioc-devel] "extra" unit tests
I think we need to think about this in the long term. Can we add support for these major tests in the build system, perhaps not every day, but every week or month? The alternative, that it is up to the developer, is not great I think. We should still advocate for people writing quicker tests, but there are some things which just take time. The advantage of the build system is that it gets tested on the official 3 platforms, with official setup. Best, Kasper On Wed, Oct 25, 2017 at 11:27 AM, Michael Lawrence <
lawrence.michael at gene.com> wrote:
Looks like BiocCodeTools should start checking whether people are using that and at least make a NOTE of it. On Tue, Oct 24, 2017 at 8: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]]
_______________________________________________ Bioc-devel at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/bioc-devel
[[alternative HTML version deleted]]
_______________________________________________ Bioc-devel at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/bioc-devel