hi, I was experimenting with 'inspect', these are the steps I followed up to now, it's the standard trial and error of the lazy impatient:
altered doRUnit.R:
## Run
tests <- inspect(runTestSuite(testSuite), track=track)
but then all tests fail
went to CRAN and checked most packages depending on RUnit and found none that was using 'inspect'. (for the record, these are the packages I examined: fUnitRoots, RSQLite, graph, Rcpp, BLCOP, RProtoBuf, RcppArmadillo, fArma, fAsianOptions, operator.tools, operators, plyr, sprint, surveillance, timeDate, timeSeries)
then went into the source code and found the place where the test is invoked... and added a note to myself...
## TODO: add tracker data collection
.tracker$init()
## ordinary test function execution:
timing <- try(system.time(inspect(func(), track=.tracker))
then came here and saw a comment dating back to 2007-11-27 where Matthias states:
»please note that the inspect mechanism is not heavily
»used and tested as it is rather impractical as only one function call at
»a time can be tracked. This is far from being a code coverage tool.
can we work at it? I kind of need a code coverage tool and I already use RUnit for unit testing.
a relevant discussion:
https://sourceforge.net/mailarchive/forum.php?thread_name=c0177e5a0711241846j6d5688e0i152debb08033c43c%40mail.gmail.com&forum_name=runit-help