{testthat} is great for automatic testing. Here are some tricks for the heavy user: https://blog.r-hub.io/2020/11/18/testthat-utility-belt/ #rstats #testing #unittest #testthat
Helper code and files for your testthat tests - R-hub blog

If your package uses testthat for unit testing, as many packages on CRAN, you might have wondered at least once about where to put โ€œthingsโ€ you wished to use in several tests: a function generating a random string, an example image, etc. In this blog post, we shall offer a round-up of how to use such code and files when testing your package. Code called in your tests Remember our post about internal functions in R packages? What about internal functions in unit tests of R packages? And code that needs to be run for tests?

Its good to have many tests in your R package, but it can be a pain to debug some failing tests when it happens. {lazytest} for the rescue: only rerun the failing tests, until they pass: https://lazytest.cynkra.com/ #RStats #testthat #lazy
Runs Only Failed Tests

A companion package to the testthat package that saves development time by helping you rerun only the tests that have failed during the last run.

From RUnit to testthat with Coding Agent Support | Mirai Solutions GmbH

We present an interesting case study: we migrated the test suite of our R package ๐—ซ๐—Ÿ๐—–๐—ผ๐—ป๐—ป๐—ฒ๐—ฐ๐˜ from ๐—ฅ๐—จ๐—ป๐—ถ๐˜ to ๐˜๐—ฒ๐˜€๐˜๐˜๐—ต๐—ฎ๐˜ using ๐—”๐—œ-๐—ฝ๐—ผ๐˜„๐—ฒ๐—ฟ๐—ฒ๐—ฑ ๐—ฐ๐—ผ๐—ฑ๐—ถ๐—ป๐—ด ๐—ฎ๐—ด๐—ฒ๐—ป๐˜๐˜€s. We used ๐—š๐—ผ๐—ผ๐—ด๐—น๐—ฒ ๐—๐˜‚๐—น๐—ฒ๐˜€, an asynchronous coding agent, to handle the repetitive, multi-file refactoring work. The process wasn't just about automation, it required careful context preparation, environment setup, and iterative prompt engineering. Key ๐˜๐—ฎ๐—ธ๐—ฒ๐—ฎ๐˜„๐—ฎ๐˜†๐˜€:   โ€ข AI agents excel at tedious, semantics-aware tasks (like fixing ๐˜ฆ๐˜น๐˜ฑ๐˜ฆ๐˜ค๐˜ต_๐˜ฆ๐˜ฒ๐˜ถ๐˜ข๐˜ญ argument order across dozens of files)   โ€ข Managed VM environments reduce risks while maintaining utility   โ€ข Combining different AI tools (Jules + Aider) provided robust validation through "third-party" code review This results in a faithfully migrated test suite with equivalent coverage and behavior, achieved faster and with more confidence. Read about our process, challenges, and solutions in our news post. https://lnkd.in/d-QUGDJ4 #rstats #SoftwareDevelopment #AIEngineering #TestAutomation #OpenSource

Discover the power of property-based testing in R with the #quickcheck package! Seamlessly integrates with #testthat and offers a variety of generators for atomic vectors, lists, and tibbles. Perfect for ensuring your code's reliability. Check it out: https://github.com/armcn/quickcheck #rstats #rprogramming #testing
GitHub - armcn/quickcheck: Property Based Testing in R

Property Based Testing in R. Contribute to armcn/quickcheck development by creating an account on GitHub.

GitHub
{testthat} is great for automatic testing. Here are some tricks for the heavy user: https://blog.r-hub.io/2020/11/18/testthat-utility-belt/ #rstats #testing #unittest #testthat
Helper code and files for your testthat tests - R-hub blog

If your package uses testthat for unit testing, as many packages on CRAN, you might have wondered at least once about where to put โ€œthingsโ€ you wished to use in several tests: a function generating a random string, an example image, etc. In this blog post, we shall offer a round-up of how to use such code and files when testing your package. Code called in your tests Remember our post about internal functions in R packages? What about internal functions in unit tests of R packages? And code that needs to be run for tests?

Its good to have many tests in your R package, but it can be a pain to debug some failing tests when it happens. {lazytest} for the rescue: only rerun the failing tests, until they pass: https://lazytest.cynkra.com/ #RStats #testthat #lazy
Runs Only Failed Tests

A companion package to the testthat package that saves development time by helping you rerun only the tests that have failed during the last run.

Discover the power of property-based testing in R with the #quickcheck package! Seamlessly integrates with #testthat and offers a variety of generators for atomic vectors, lists, and tibbles. Perfect for ensuring your code's reliability. Check it out: https://github.com/armcn/quickcheck #rstats #rprogramming #testing
GitHub - armcn/quickcheck: Property Based Testing in R

Property Based Testing in R. Contribute to armcn/quickcheck development by creating an account on GitHub.

GitHub
{testthat} is great for automatic testing. Here are some tricks for the heavy user: https://blog.r-hub.io/2020/11/18/testthat-utility-belt/ #rstats #testing #unittest #testthat
Helper code and files for your testthat tests - R-hub blog

If your package uses testthat for unit testing, as many packages on CRAN, you might have wondered at least once about where to put โ€œthingsโ€ you wished to use in several tests: a function generating a random string, an example image, etc. In this blog post, we shall offer a round-up of how to use such code and files when testing your package. Code called in your tests Remember our post about internal functions in R packages? What about internal functions in unit tests of R packages? And code that needs to be run for tests?

Its good to have many tests in your R package, but it can be a pain to debug some failing tests when it happens. {lazytest} for the rescue: only rerun the failing tests, until they pass: https://lazytest.cynkra.com/ #RStats #testthat #lazy
Runs Only Failed Tests

A companion package to the testthat package that saves development time by helping you rerun only the tests that have failed during the last run.

Discover the power of property-based testing in R with the #quickcheck package! Seamlessly integrates with #testthat and offers a variety of generators for atomic vectors, lists, and tibbles. Perfect for ensuring your code's reliability. Check it out: https://github.com/armcn/quickcheck #rstats #rprogramming #testing
GitHub - armcn/quickcheck: Property Based Testing in R

Property Based Testing in R. Contribute to armcn/quickcheck development by creating an account on GitHub.

GitHub