Mark van der Loo

The other option is to generate the rules in a file and read them later. ```r template

Hi, I think this would be out of scope for the package. Regarding the warnings/errors generated during validation, you can have them thrown by setting an option, `validate(data, rules, raise="all"`)

Thanks for this. Will look into that!

I'm not familiar with those `testthat` features (never used them), but I'll have a look. One thing you can do is to add `setup.R` to your `tinytest` directory. You can...

Oh, by the way. If you call `options()` literally in your test file, these options are reset automatically when the test file is finished. (see vignette). Same for environment variables....

I think I can scan the folder where the test file resides for a file called `setup.R` and afterwards for a file called `breakdown.R`. Because of the parallelization & design...

Hi Sebastian. Regarding a setup and teardown script. If it was to be implemtented in tinytest, it would be sourced automatically by `run_test_file()` to ensure that a file run remains...

Hi there! You can use as.data.frame() on the output (tinytest object), and that can be translated to JSON using e.g. the JSONLite package. I've been meaning to look into standardized...

Cool! I think that a separate package is actually a great idea. This would both keep things tiny for the user and still give the opportunity to integrate with JUnit...

Awesome! I advertised a little bit: https://twitter.com/markvdloo/status/1667069773119717376?s=20 and https://mathstodon.xyz/@markvanderloo/110513061667258127