search for: test_packag

...package:graphics" "package:grDevices" [7] "package:utils" "package:datasets" "package:methods" [10] "Autoloads" "package:base" My question is this: when I execute the test function in devtools function it calls the the test_package function in the testthat package - but that function is located higher up the search path - how does R find it? (I ask this question because I'm trying to simulate package loading from within R to simplify the development cycle, but something is missing in my knowledge of namespaces, and so I...

...* all expectations now give more information on failure to make it easier to track down the problem. * test_file and test_dir now run in code in separate environment to avoid pollution of global environment. They also temporary change the working directory so tests can use relative paths. * test_package makes it easier to run all tests in an installed package. Code run in this manner has access to non-exported functions and objects. If any errors or failures occur, test_package will throw an error, making it suitable for use with R CMD check. -- Assistant Professor / Dobelman Family Juni...

...* all expectations now give more information on failure to make it easier to track down the problem. * test_file and test_dir now run in code in separate environment to avoid pollution of global environment. They also temporary change the working directory so tests can use relative paths. * test_package makes it easier to run all tests in an installed package. Code run in this manner has access to non-exported functions and objects. If any errors or failures occur, test_package will throw an error, making it suitable for use with R CMD check. -- Assistant Professor / Dobelman Family Juni...

...de): git clone http://jcborras at github.com/jcborras/rseedpkg.git rseedpkg builds and installs with the usual sequence: R CMD build rseedpkg R CMD INSTALL rseedpkg_0.01-1.tar.gz Last but not least one can test it from the command line: Rscript --verbose --default-packages=testthat,log4r -e "test_package('rseedpkg')" The thing is that if one changes the call log4r:::debug() to plain debug() in R/f1.r and R/f2.r then one ends up calling base:::debug() and not log4r:::debug() even though the former should be masked by the later as log4r is a package dependency of my dummy rseedpkg. And...

...anage packages dependencies. That way batch checking packages would be easier, as required dep metadata would be at hand in description file. Batch checking pkgs with all their suggests will simply result into testing whole CRAN. In a single package it can be handled with `if (requireNamespace(.)) test_package(.)` for `testthat` and `knitr`, also with mocking up `.Rout` files. But I'm interested into canonical design of a suggested package and `_R_CHECK_FORCE_SUGGESTS_` env var. Is there any R core dev team recommendation/suggestion on that? and don't you thing new field `testChecker` in DESCRI...

I am trying to learn how to run the unit tests in the stringr package and have the following questions. 1) The r-cran-stringr package does not suggest/depend on the r-cran-testthat package . Would it make sense to add such a thing since after all the tests in /usr/lib/R/site-library/stringr/tests rely on testthat package? 2) I am getting the following error when trying to run the unit tests %

...ing packages would be easier, as required dep > > metadata would be at hand in description file. Batch checking pkgs > > with all their suggests will simply result into testing whole CRAN. > > > > In a single package it can be handled with `if (requireNamespace(.)) > > test_package(.)` for `testthat` and `knitr`, also with mocking up > > `.Rout` files. > > > > But I'm interested into canonical design of a suggested package and > > `_R_CHECK_FORCE_SUGGESTS_` env var. > > Is there any R core dev team recommendation/suggestion on that? and >...

...> That way batch checking packages would be easier, as required dep > metadata would be at hand in description file. Batch checking pkgs > with all their suggests will simply result into testing whole CRAN. > > In a single package it can be handled with `if (requireNamespace(.)) > test_package(.)` for `testthat` and `knitr`, also with mocking up > `.Rout` files. > > But I'm interested into canonical design of a suggested package and > `_R_CHECK_FORCE_SUGGESTS_` env var. > Is there any R core dev team recommendation/suggestion on that? and > don't you thing new...

...creating a testing environment that is philosophically centred in R. Version 0.6 ------------------------------------------------------------------------------ * All `mutatr` classes have been replaced with ReferenceClasses. * Better documentation for short-hand expectations. * `test_dir` and `test_package` gain new `filter` argument which allows you to restrict which tests are run. -- Assistant Professor / Dobelman Family Junior Chair Department of Statistics / Rice University http://had.co.nz/ _______________________________________________ R-packages mailing list R-packages at r-project.or...

...creating a testing environment that is philosophically centred in R. Version 0.6 ------------------------------------------------------------------------------ * All `mutatr` classes have been replaced with ReferenceClasses. * Better documentation for short-hand expectations. * `test_dir` and `test_package` gain new `filter` argument which allows you to restrict which tests are run. -- Assistant Professor / Dobelman Family Junior Chair Department of Statistics / Rice University http://had.co.nz/ _______________________________________________ R-packages mailing list R-packages at r-project.or...

Dear Raju I agree to Dirk that this is not really the best place for these matters, but as I got curious, I checked and found you should use test_package() and not test_dir(), as the latter does not load unexported functions of the package (such as check_string()) that may occur in the tests. For packaging of r-cran-stringr, it is probably most efficient to file a bug report there because of the missing Suggests for r-cran-testthat. Kind regar...

...ter html StopReporter html SummaryReporter html TapReporter html TeamcityReporter html auto_test html auto_test_package html compare html compare_state html comparison-expectations html context html describe html dir_state...

...html > StopReporter html > SummaryReporter html > TapReporter html > TeamcityReporter html > auto_test html > auto_test_package html > compare html > compare_state html > comparison-expectations html > context html > describe html &...