similar to: New package: RUnit

Hello R developers, installing R 2.0.0 from source on a Linux Debian system (gcc 3.2.2) - which worked just fine - I encountered the following problem when trying to update/install packages with the option --with-package-versions: example: RUnit 0.4.0 (also on CRAN) R20 CMD INSTALL -l /mnt/local/R/R-2.0.x-libs-EpiR --with-package-versions RUnit_0.4.0.tar.gz or after untaring R20 CMD INSTALL

Having used JUnit and PyUnit, I was pleased to see the release of the RUnit package on CRAN. I'm wondering if there are any RUnit users out there that would be willing to share some tips on how they organize their code to work with RUnit. Specifically, I'm wondering about the best way to load/import/source the functions to be tested. I would like to end up with a script, testall or some

There appears to be a bug in RUnit. Given a testsuite testsuite.math, say, when I run: runTestSuite(testsuite.math) this works fine, provided there are no extraneous files in the unit test subdirectory. But if there are any Emacs temp files (with names that end with '~') then runTestSuite gets confused and tries to run functions from the temp files as well. [[alternative HTML version

Hi, after updating R 2.5.0 devel yesterday we today observed many new unexpected failures in our daily package build and test system runs, which can be traced to recent changes in the implementation in try() (as noted in NEWS). Investigating this new implementation I come across an issue in conjuntion with using S4 classes and methods. try(expr) does not return an object with attribute

Dear R-help group, I have a two-way ANOVA with two crossed random factors, no nesting. Each factor has three levels, resulting in 9 cells for the experiment. Each cell contains 10 repetitions. According to the ANOVA model I assume equal variances for all levels per factor. I would like to get REML-estimates for the variances of the two factors and moreover get confidence intervals for these

Hi, trying to install a package containing C code and requiring non-default configure argument settings the incantation (this has worked for R <= 2.8.1 on the same architectures) R CMD INSTALL --configure-args="--with-opt1 --with-opt2" packname does always result in a warning Warning: unknown option '--with-opt2' and consequently the option is ignored. Reverting the order

Hi! I'm puzzled by the return value of ifelse consider x<-integer(0) ifelse(is(x, "character"), paste(x), x) [1] NA whereas if (is(x, "character")) return(paste(x)) else x [1] integer(0) or x<-integer(1) ifelse(is(x, "character"), paste(x), x) [1] 0 work as I had anticipated. Is this correct behaviour? Regards, Matthias >sessionInfo() R

Hi! >getNamespaceExports("base") Error in ls(NULL, all = TRUE) : using 'as.environment(NULL)' is defunct getNamespaceExports function (ns) { ns <- asNamespace(ns) if (isBaseNamespace(ns)) ls(NULL, all = TRUE) else ls(getNamespaceInfo(ns, "exports"), all = TRUE) } <environment: namespace:base> One possible way to fix this could be

Hi, we noticed that since some time after Aug 24th the daily snapshots provided on ftp://ftp.stat.math.ethz.ch/Software/R/ no longer have their default tarball file name but dropped the date stamp, i.e. R-devel_.tar.bz2 Same for R-patched snapshots. Could one of the maintainers please take a look. We rely on the default naming convention for automatic builds. Regards, Matthias --

Hi, since a couple of days ago I see failures when using R CMD INSTALL -l lib path-to-src/pkg.tar.gz This occurs in automated library updating via a shell script and is caused by the immediate preceding call to leave an 00LOCK folder even though the package installation of that call succeeded. This occurs at random (no obvious/systematic correlation to package name or or such) and only for

Hi all, I'm a little surprised at > NULL == c("a", "b") logical(0) > all(NULL == c("a", "b")) [1] TRUE Reading the documentation for all() this was not clear for me to be expected. Originally the question came up when using > match.arg(NULL, c("a", "b")) [1] "a" where I had thought an error would occur. So

Hi, I wonder whether a package with namespace & dynamic library can be installed with the version number attached, ie. with the argument --with-package-versions. Is this currently possible? Using R 1.9.1 on Debian 3.0 I encounter a problem when trying to load a package installed with R91 CMD INSTALL --with-package-versions -l /mnt/local/R/R-1.9.x-libs-EpiR RIO in R started with R91

I''d like to announce the first release of capistrano-runit-tasks. This came about as I wanted to use runit rather than spinner/spawner/ reaper on my memory limited VPS but should be useable for any setup. From the README: This library extends Capistrano to allow processes to be supervised using the runit package. It replaces some of the standard tasks with runit versions and

Greetings - I'm finally finished review, here's what I heard: ============ from Tobias Verbeke: anthony.rossini@novartis.com wrote: > Greetings! > > After a quick look at current programming tools, especially with regards > to unit-testing frameworks, I've started looking at both "butler" and > "RUnit". I would be grateful to receieve real

Hi, further down from the problem I asked about yesterday I encounter the following problem (please appologize for the lengthy mail - I have not found a brief example making the issue clear): - using R packages making use of namespaces & - S4 classes when using --with-package-versions in the install call: Pkgs install ok and the first pkg 'base' can be loaded in R

Hello! I have looked at Martin's recent work on "merging" unit tests with R CMD check, fused it with my and Tony's contributions and developed it a bit further. Take a look into the attached demo package on how it works. In essence: PKG/inst/RUnitTests |- runRUnitTests.R (script to run RUnit tests) \- ... (any RUnit test file)

Folks, An RUnit test suite is failing after all tests are complete with the following message: Error in parse(n = -1, file = file) : unexpected '}' at 620: 621: } All individual tests work when run individually, and all but one run within the RUnit test suite. What might be causing this? A similar error message during package creation was discussed earlier

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 | `-

Hi, in the process of upgrading to R 1.6.0 I tried to install the latest RMySQL (0.5-0) package (Omegahat). The following error was reported [...] gcc -I/mnt/local/R/R-1.6.0/lib/R/include -I/usr/include/mysql -I/usr/local/include -D__NO_MATH_INLINES -mieee-fp -fPIC -g -O2 -c RS-MySQL.c -o RS-MySQL.o RS-MySQL.c: In function `RS_MySQL_newConnection': RS-MySQL.c:203:

R-developers Does anybody know how I incorporate the use of the tracker in RUnit in the unit tests? I have read the RUnit Vignette, help pages and searched around, but I could find no examples of using 'inspect' in the unit test functions. Moreover, doing so, I tried something like library(RUnit) myFunction <- function(x) { return(x) } track <- tracker() track$init()