search for: test_check

...;) > req$status_code > }, > error = function(e){ > -1 > } > ) > } > ## test package separated with filter due to limited Travis-CI build time > ## HTTP status 200 indicates ?OK? > if(curl::has_internet() & check_qrng() == 200){ > test_check('qrandom', filter = "qrandom") > test_check('qrandom', filter = "qrandomunif") > test_check('qrandom', filter = "qrandomnorm") > test_check('qrandom', filter = "qUUID") > test_check('qrandom', fi...

..., and you'd also have to prepare >>> another CRAN submission just to have those tests run. It's also against >>> CRAN policy to knowingly submit a package with unfixed ERRORs. >>> >>> (Currently, R can only tell you that the tests hung in the >>> test_check('rlibkriging') call in the tests/testthat.R, which isn't >>> precise enough.) >> >> You can specify a different "reporter" in the test_check() call, and it >> will print more useful information.? I don't think there's a perfect >> one,...

...the testthat harness, and you'd also have to prepare >> another CRAN submission just to have those tests run. It's also against >> CRAN policy to knowingly submit a package with unfixed ERRORs. >> >> (Currently, R can only tell you that the tests hung in the >> test_check('rlibkriging') call in the tests/testthat.R, which isn't >> precise enough.) > > You can specify a different "reporter" in the test_check() call, and it > will print more useful information.? I don't think there's a perfect > one, but > > ?...

...> work outside the testthat harness, and you'd also have to prepare > another CRAN submission just to have those tests run. It's also against > CRAN policy to knowingly submit a package with unfixed ERRORs. > > (Currently, R can only tell you that the tests hung in the > test_check('rlibkriging') call in the tests/testthat.R, which isn't > precise enough.) You can specify a different "reporter" in the test_check() call, and it will print more useful information. I don't think there's a perfect one, but test_check('rlibkriging',...

...and you'd >>> also have to prepare another CRAN submission just to have those >>> tests run. It's also against CRAN policy to knowingly submit a package with unfixed ERRORs. >>> >>> (Currently, R can only tell you that the tests hung in the >>> test_check('rlibkriging') call in the tests/testthat.R, which isn't >>> precise enough.) >> >> You can specify a different "reporter" in the test_check() call, and >> it will print more useful information.? I don't think there's a >> perfect on...

I have seen some basic examples of using Mocha and Stubba with ActiveRecord Models; However, the ones I read were somewhat simplistic. That is they stubbed the find class method of the model, or the execute method of the connection object. While stubbing the find method had the desired effect for the author it did not help with a situation I was hacking away on. Which was writing a test case

...>>> also have to prepare another CRAN submission just to have those >>>> tests run. It's also against CRAN policy to knowingly submit a package with unfixed ERRORs. >>>> >>>> (Currently, R can only tell you that the tests hung in the >>>> test_check('rlibkriging') call in the tests/testthat.R, which isn't >>>> precise enough.) >>> >>> You can specify a different "reporter" in the test_check() call, and >>> it will print more useful information.? I don't think there's a >&g...

...y have to rewrite the tests to work outside the testthat harness, and you'd also have to prepare another CRAN submission just to have those tests run. It's also against CRAN policy to knowingly submit a package with unfixed ERRORs. (Currently, R can only tell you that the tests hung in the test_check('rlibkriging') call in the tests/testthat.R, which isn't precise enough.) These lines look a bit scary: tests/testthat/bench-KrigingFit.R: pack=list.files(file.path("bindings","R"),pattern = ".tar.gz",full.names = T) install.packages(pack,repos=NULL) te...

...mo()' for some demos, 'help()' for on-line help, or 'help.start()' for an HTML browser interface to help. Type 'q()' to quit R. > library(testthat) Warning message: package 'testthat' was built under R version 3.3.3 > library(bwt) > > test_check("bwt") Error: No tests found for bwt Execution halted * DONE I checked the package and it had no tests subfolder. Yet -as far as I can judge- CRAN tried to run tests anyway and error'd when there were none to be found. This would make sense of adding tests was obligatory, but I c...

...ocessed. The auto-check found additional issues for the *last* version released on CRAN: clang-UBSAN < https://www.stats.ox.ac.uk/pub/bdr/memtests/clang-UBSAN/bigKRLS> gcc-UBSAN <https://www.stats.ox.ac.uk/pub/bdr/memtests/gcc-UBSAN/bigKRLS> Clicking through, you find that > test_check("bigKRLS") gauss_kernel.cpp:38:40: runtime error: member call on address 0x6120001f2c40 which does not point to an object of type 'BigMatrix' 0x6120001f2c40: note: object is of type 'FileBackedBigMatrix' [details omitted] SUMMARY: UndefinedBehaviorSanitizer: undefined-...

Dear testers, 3.9.0-rc1 was just tagged from the 3.9 branch at r277207. This took a little longer than I'd hoped, but I think the branch is in a decent state now. There are still open merge requests and bugs, but I'd like to get the real testing started to see where we're at. Please build, test, and upload binaries to the sftp. Let me know how it goes. I'll upload source, docs,

...w result: ERROR >???? Running ?testthat.R? [55s/138s] >?? Running the tests in ?tests/testthat.R? failed. >?? Complete output: >???? > Sys.setenv("R_TESTS" = "") >???? > >???? > library(testthat) >???? > library(drake) >???? > >???? > test_check("drake") >???? 1. Failure: function_dependencies() works on :: and ::: > (@test-namespaced.R#19) >???? sort(find_namespaced_functions(crazy)) not equal to `ns`. >???? Lengths differ: 0 vs 7 > > >???? 2. Failure: function_dependencies() works on :: and ::: > (@test-...

Thank you for your answer. In facts, 10 threads are asked by armadillo for some LinAlg, which backs to two threads as warned. But I cannot imagine this costs so much time just for that... A deeper analysis of time spent seems to point that a large time was mainly spent on testthat and Rcpp dependencies compilation... But other recent packages depending on these also are not spending so much time.

...t;assert.h> #include <unistd.h> #include <signal.h> #include <openssl/bn.h> #if defined(HAVE_STRNVIS) && defined(HAVE_VIS_H) && !defined(BROKEN_STRNVIS) # include <vis.h> #endif #include "test_helper.h" #include "atomicio.h" #define TEST_CHECK_INT(r, pred) do { \ switch (pred) { \ case TEST_EQ: \ if (r == 0) \ return; \ break; \ ca...