similar to: RUnit - need advice on a good directory structure or tips...

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

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, I'm pretty much an R noob and I'm missing some paradigm in R I think. I can't figure our how to compare numerics. here's a transcript of my tests. Any pointers? > print(range_sd) [1] 34.40783 > is.numeric(range_sd) [1] TRUE > is.numeric(foo) [1] TRUE > is.double(range_sd) [1] TRUE > is.double(foo) [1] TRUE > > identical(range_sd, foo) [1]

I want to get path profiling information with LLVM. LLVM provides methods for path profiling.I also get the llvmprof.out successfully. So I want to output the result.With llvm-prof ,I get the error:llvm-prof: Unkknown packet #5. So I have to write my own pass to output the path profiling result,the following is my kernel codes:

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

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

As others have mentioned, Chapter 4 of David A. Black''s book _Ruby for Rails_ is now available for download from the Manning site. The fact that the book is being released one chapter at a time makes it easy to read in small, digestible chunks. I never intended to review every chapter individually here, but now that I''ve done the first three, I feel like I ought to continue.

Hello, I would like to compress a long string (character vector), store the compressed string in the text field of a SQLite database (using RSQLite), and then load the text back into memory and decompress it back into the the original string. My character vector can be compressed considerably using standard gzip/bzip2 compression. In theory it should be much faster for me to compress/decompress

Hi, I have conventional directory structure for a pass taken from project examples. I want to build a tool which makes usage of a shared library which is included in the project. This means that I have library here: # lib/foo/*.cc and after compilation the library is placed here # Debug/lib/libfoo.so My tool is located here: # tool/test_foo # cat tool/Makefile LEVEL = ../ TOOLNAME=test_foo

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

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

We would like to announce the availability on CRAN of a new package: RUnit It contains a unit testing framework strongly inspired by Javas popular JUint package. In addition it contains some functionality to investigate the degree to which some function is covered by a test suite. The main aims of the package are - to support a development style where test cases are written and constantly

We would like to announce the availability on CRAN of a new package: RUnit It contains a unit testing framework strongly inspired by Javas popular JUint package. In addition it contains some functionality to investigate the degree to which some function is covered by a test suite. The main aims of the package are - to support a development style where test cases are written and constantly

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

Hello, all. There is a problem to get an output of warnings() function to sink in a file specified. There are to files 1. File "test" with content: source("test_foo",local=T) 2. and file "test_foo" with content: options(warn = 1) sink("c:/temp/foo.txt",append=F) warning("Foo warning") warnings() sink() 3. If I run R as "c:\Program

Hi! Currently both, the controller/functional tests and mailer tests, contain a lot of cruft. I''ve created two superclasses to DRY them up a bit. Here are some examples how tests using those superclasses will look: http://pastie.caboo.se/66139 Ticket with the patch: http://dev.rubyonrails.org/ticket/8521 Known issues: * Since we don''t explicitly setup the @request and

Just released a very simple plugin for including all fixtures in your tests. Once you have a large number of table, manually managing the fixtures for every single test stub can be quite tedious. Use as follows class BlogArticleTest < Test::Unit::TestCase all_fixtures def test_foo ... end end Couldn''t be easier. More info here: