similar to: R CMD check and RUnit

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)

I made my own RUnit testing convention, and I want to introduce this to one of my friends. Before that, I'd like to review my codes. The problem that I met when I tried to polish my codes is: How can I get the file path in the file??? I.e., I want to get the path to the file that I'm writing using some magic R functions. But I couldn't find any good magic. Is there any magic? So, I

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

Hello, I'm writing a script that automates the testing of reverse dependencies of a package. I found the function testInstalledPackage in the tools package, which seems to do what I want. However, when I use it for a source package that was installed with --install-tests, I've noticed that only the actual test files (e.g. located in inst/tests) are available and run. In other words the

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

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

I''d like to announce the second release of capistrano-runit-tasks, available from http://rubyforge.org/projects/cappy-runit/ It now supports: * File based templates * sv as the service control command in addition to runsvctrl * A much simpler interface for creating additional services. More work still needs to be done though! == TODO * Allow add_service to create more than one

Hi, I''m deploying Unicorn on a Rails application with RUnit. Technically I''m using Chef''s deployment tools, if any of you are familiar with it (https://github.com/opscode-cookbooks/application_ruby) but to be clear they aren''t doing anything magical, so this is purely an issue with RUnit and Unicorn. The TL;DR of the following post, which has lots of

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

Hello! I am building a package, which includes also one Fortran subroutine, which works fine if I compile it as a shared library and load it into R via dyn.load(). However, when I launch R CMD check it doesn't stop with checking examples. It's just doing and doing ... I pasted the whole output from R CMD check. Does anyone have any suggestions? I'm still using R 2.0.1.

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()

Hello R users! I just found out that I have 49 invitations for Gmail (gmail.google.com). I have been using it now for a while and is really nice. Don't forget 1 GB for free. I will invite those who respond to this mail by FIFO. -- Lep pozdrav / With regards, Gregor Gorjanc ------------------------------------------------------------------------ University of Ljubljana Biotechnical

Hello! I have just discovered a possible bug or lack of my knowledge. The last option is not so uncommon and I decided to ask here before flooding the bugs repository. Say I have a package test with vignette. Moving package directory to some other name, say test2, fails R CMD check with $ R CMD check test2 * checking for working latex ... OK * using log directory

Hello! Those of you, who use Sweave a lot, will probably find my shell script usable. You can get it at: http://www.bfro.uni-lj.si/MR/ggorjan/programs/shell/Sweave.sh No warranty, however don't hesitate to contact me if you find an error or have a patch! -- Lep pozdrav / With regards, Gregor GORJANC --------------------------------------------------------------- University of

Hello! Say I have a function foo1, which has argument ... to pass various arguments to foo2 i.e. foo1 <- function(x, ...) { foo2(x, ...) } Say that foo2 accepts argument arg1 and I would like to do the following: - if foo1 is called as foo1(x) then I would like to assign some value to arg1 inside foo1 before calling foo2 arg1 <- "some value" foo2(x, arg1=arg1) - if foo1 is

Ivan, thank you for the tips; they allowed me to move on to the next problems. By building the tar file first and checking it later, and fixing several other problems I got R CMD check to work. It does *not* delete inst/doc. It also does not run boostrap.R, as far as I can tell, presumably because only devtools does. Check within RStudio continues to delete inst/doc, so this behavior is

Hello Does anybody have any advice, or even some ready-made configuration, for running logcheck on svlogd log files? svlogd is the logging daemon provided by runit, a replacement for sysv init with service supervision. svlogd, and thus runit, are incompatibile with vanilla logcheck, because svlogd logfiles are rotated when they reach a certain size, not at a certain time. Therefore when logcheck

Hello! I was just wondering if Sweave can work with \input or \include LaTeX commands. So, is it aware of such a possible hierarchy in documents. I would test that, but I don't have such a report available at the moment. I thought of that when I was writting shell script for Sweave from command line and I have solved that part there. -- Lep pozdrav / With regards, Gregor GORJANC

Hello! I was reading R-intro and I have some suggestions: R-intro.html#A-sample-session rm(fm, fm1, lrf, x, dummy) suggestion rm(fm, fm1, lrf, x, y, w, dummy) The next section will look at data from the classical experiment of Michaelson and Morley to measure the speed of light. file.show("morley.tab") mm <- read.table("morley.tab") suggestion mm <- data(morley)