search for: test_that

...n some significant changes under the hood. Our package has migrated to using Roxygen for function documentation---a move that was greatly facilitated by the Rd2roxygen package written by Yihui Xie and Hadley Wickham. Our homebrewed testsuite has also been re-written on top of Hadley's excellent test_that package. ?Many thanks to the R community for writing great tools to support package development! The full changelog is appended to this email. For a detailed diff of changes since 0.5.3, see: ??https://github.com/Sharpie/RTikZDevice/compare/0.5.3...master With 80 commits, it is likely we introduc...

...n some significant changes under the hood. Our package has migrated to using Roxygen for function documentation---a move that was greatly facilitated by the Rd2roxygen package written by Yihui Xie and Hadley Wickham. Our homebrewed testsuite has also been re-written on top of Hadley's excellent test_that package. ?Many thanks to the R community for writing great tools to support package development! The full changelog is appended to this email. For a detailed diff of changes since 0.5.3, see: ??https://github.com/Sharpie/RTikZDevice/compare/0.5.3...master With 80 commits, it is likely we introduc...

Hi there, I have some unused code in my project but have no idea how to clean it up in some kind of automatic way. Maybe there are some tools/ways to identify and remove/mark dead parts of the code? Thanks in advance! Kind regards, Alex

...ntext("altrep") length_func<-function(x){ return(length(x)) } setAltClass(className = "test", classType = "real") setAltMethod(className = "test", getLength = length_func) testData = runif(10) myAltrep = makeAltrep("test", testData) test_that("Auto serialize", { browser() A = 10 A_serialized=serialize(A,NULL) B = new.env() B_serialized=serialize(B,NULL) }) ``` There is nothing but two variables A and B in the test function. I use browser() to stop and debug the code. Here is the weird thing, my pack...

.... My primerTree package (2013) was originally primer_tree, but I had to change the name to camelCase to comply with the check requirements. Using camelCase in the package name makes reading code jarring, as the functions all use snake_case. 2. The widely used testthat package would likely be called test_that, like the corresponding function within the package. This also highlights one of the drawbacks of the current situation, without separators the package name is more difficult to read, does it have two t's or three? 3. The assertive suite of packages use `.` for separation, e.g. `assertive.base`...

On 09/08/2019 4:37 p.m., Gabriel Becker wrote: > Duncan, > > > On Fri, Aug 9, 2019 at 1:17 PM Duncan Murdoch <murdoch.duncan at gmail.com > <mailto:murdoch.duncan at gmail.com>> wrote: > > On 09/08/2019 2:41 p.m., Gabriel Becker wrote: > > Note that this proposal would make mypackage_2.3.1 a valid > *package name*, > > whose

...ir html test_env html test_examples html test_file html test_package html test_path html test_that html testthat html testthat_results html try_again html use_catch html watch html wit...

...html > test_env html > test_examples html > test_file html > test_package html > test_path html > test_that html > testthat html > testthat_results html > try_again html > use_catch html > watch...