nsamidnight.blogg.se

Winbuilder scripts
Winbuilder scripts





If you want to keep debugging code for future use, but let the state clean once everything is set up for CRAN, use a parameter in your tests.įor instance, here is a part of my unit test code for with condition for debug: # debug if problems with CRAN to retrieve outputs However, here, you’re doing it for debugging.

winbuilder scripts

You are supposed to let a clean state after you leave tests. Saving files inside the “testthat/” directory is a practice to avoid for a submission. Note that some files format are not downloadable from the server, this is why I recommend a zip file. Then, on the Win-Builder page dedicated to your package, you will be able to download it and explore it locally. Compress these files in a zip file using utils::zip() inside this same directory.

winbuilder scripts winbuilder scripts

Save all meaningful, intermediate outputs that you want to open or run locally after download. To debug your code on Win-Builder, you can create unit tests that save outputs inside the “testthat/” directory.







Winbuilder scripts