similar to: Behavior of --install-tests and testInstalledPackage

Background: I run tools::testInstalledPackage on all packages that dependend on survival (605 as of today) before sending a new release to CRAN. It has a few false positives which I then follow up on.? (Mostly packages with as-yet-incomplete tests in their inst directory). ?Issue: testInstalledPackage("mets")? generates an? "Error in checkVignettes(pkg, lib.loc, latex = FALSE,

Hi! I appologize for crossposting, but this might be of broader interest. In case you are interested in fusing RUnit with R CMD check under unix alike OS, here is one way of doing/hacking this. My aim was to perform unit tests: (1) during R CMD check (2) at any other time Say you have a package PKG in a map PKG. I use the following structure PKG |- R |- ... |- inst | |- doc | `-

I installed R version 2.15.0 under C:/ on a PC running Windows 7.  When I load library("tools") to test the installation and then run the command testInstalledPackages("base"), I get the following error: Error in setwd(outDir): cannot change working directory. I have set up the R shortcut to run it as administrator. [[alternative HTML version deleted]]

On 5/3/16 11:29 AM, Thierry Onkelinx wrote: > Dear Mick, > > Note that both knitr and rmarkdown are listed under Suggests: both are > required to compile the vignette. Installing rmarkdown should solve > the problem. If not, please provide more information. OS, R version, > digest version, ... > > This is occurring in the context of an automated testing environment that

Dear group, ? When running the installation test: ? testInstalledPackages("both",outDir='c:/Test') ? I got the following message: Running ?testci.R? comparing ?testci.Rout? to ?testci.Rout.save? ... files differ in number of lines: Please note the test does not result in 'OK' as do the other tests.? Is this a concern? Regards, ???-Cody Hamilton

Hello, Section 4.3.2 of the R language definition [1] states that argument matching to formal arguments is a 3-pass process to match arguments to a function. An error is generated if any (supplied) arguments are left unmatched. Interestingly the opposite is not true as any unmatched formals does not generate an error. > f <- function(x,y,z) x > f(2) [1] 2 > f(2,3) [1] 2 Since R is

# devtools The aim of `devtools` is to make your life as a package developer easier by providing R functions that simplify many common tasks. Devtools is opinionated about how to do package development, and requires that you use `roxygen2` for documentation and `testthat` for testing. Future version will relax these opinions - patches are welcome! You can track (and contribute to) development of

# devtools The aim of `devtools` is to make your life as a package developer easier by providing R functions that simplify many common tasks. Devtools is opinionated about how to do package development, and requires that you use `roxygen2` for documentation and `testthat` for testing. Future version will relax these opinions - patches are welcome! You can track (and contribute to) development of

Hello, I'm curious to know how people log their applications in R. It seems like it's a combination of cat statements or writing out the session to a file, given the discussions I've had with people. This is fine for interactive work but is a little lacking for automated systems. To address this, I've written a logging facility modeled on the log4j Java library. The basic concept

I installed R on my Windows laptop in C:\Program Files\R\R-2.15.2 and am able to open RGUI (640bit), see packages and run commands. However, when I test the installation and run the basic tests and all the tests on the standard and recommended packages i.e.: library("tools") testInstalledBasic("both") testInstalledPackages("base", errorsAreFatal

Hi, 'revdep-rebuild' under GENTOO shows me that /usr/lib64/R/library/tkrplot/libs/tkrplot.so, which was installed at April 24th, is broken. 'ldd /usr/lib64/R/library/tkrplot/libs/tkrplot.so' shows me that tkrplot.so needs libtcl8.4.so and libtk8.4.so, which is no more installed since the installation of tcl,tk-8.5.7, which has happened at april 26th. But revdep-rebuild can't

I'm testing a new release of survival, executing the following piece of code: .... for (testpkg in survdep) { z <- testInstalledPackage(testpkg, outDir="tests") cat(testpkg, c("Ok", "Failed")[z+1], "\n", file="progress", append=T) } The vector survdep contains the names of all 156 packages listed as reverse depends on the CRAN

Dear Mick, knitr doesn't depends on rmarkdown. It's the vignette that depends on both knitr (for handle the R chunks) and rmarkdown (for the output format rmarkdown::html_vignette). https://cran.r-project.org/doc/manuals/r-release/R-exts.html#Package-Dependencies states: "The ?Suggests? field ...snip... lists packages that are not necessarily needed. This includes packages used

>From NEWS of R v2.6.0 devel: o R CMD check now does a recursive copy on the 'tests' directory. However, R CMD check does not run *.R scripts in such subdirectories (as I thought/hoped for), only those directly under tests/, This may or may not be intentional. If true, maybe the above should be clarified as: o R CMD check now does a recursive copy on the 'tests' directory

I need some help understanding a problem running the tests on the 'digest' package. Initially, I got the message that the 'knitr' package was needed to run vignettes: Running vignettes for package ?digest? Error in loadVignetteBuilder(vigns$pkgdir) : vignette builder 'knitr' not found So I installed the knitr package and all its dependents (?mime?, ?stringi?,

## the following is a dream: add some sugar syntax to allow for contracts with teeth (in and out checking) > is.positive <- function(x) (all(x>0)) > exponentiate <- function( x ::is.data.frame , exponent ::is.numeric is.positive) :: is.vector is.numeric { x$base :: is.positive ## error also if base does not exist in x; may need some special IQ x$base^exponent }

In data martedì 23 giugno 2015 23:49:54, Richard W.M. Jones ha scritto: > This allows us to test the daemon running as a host process, allowing > us to meaningfully test it using valgrind. > > This commit only adds a single test that check that the daemon starts > up, can be pinged, and exits. > --- > [...] > .gitignore | 1 + > Makefile.am

> > Generally I find it's good to look at examples that work. For > examples of packages using tests, look at source packages on CRAN. > Run the tests on them (using R CMD check), and see what gets produced. > Do you have the name of a package that use it ? I try the 10 first package, and 10 other at random, but none of them use tests... >>> Create tests/myPack.R

In data giovedì 25 giugno 2015 15:56:58, Richard W.M. Jones ha scritto: > This allows us to test the daemon running as a host process, allowing > us to meaningfully test it using valgrind. > > This commit only adds a single test that check that the daemon starts > up, can be pinged, and exits. > --- > [...]> +sub run_tests { > + my $g = Sys::Guestfs->new(); > +

Lately, when I attempted to run some of my apps, they crashed with the following output. Code: Wrong JPEG library version: library is 62, caller expects 70 I run Gentoo Linux X64. A search for the appropriate package gives this: Code: * media-libs/jpeg Latest version available: 7 Latest version installed: 7 Size of files: 949 kB Homepage: http://jpegclub.org/