Hi all,
I'm been thinking recently about the best way to incorporate testing
(regression/unit/etc) into routine data analysis scripts, both for my
own work and when teaching (e.g. a graduate-level bioinformatics class).
Conceptually it seems straightforward to incorporate tests when
developing a package or series of functions meant for reuse, but I am
wondering if there is a community-endorsed best-practice way to
incorporate this defensive programming mentality into more ad-hoc
analyses.
I'm most familiar with the defensive programming approaches in the R
world (stopifnot, testthat, assertr), but I'm most interested in general
answers to the question.
We had some discussion about this on [an
issue](https://github.com/swcarpentry/r-novice-gapminder/issues/221) in
the r-novice-gapminder repo a while back.
Thanks in advance for any input!
Best,
Naupaka
_______________________________________________
Discuss mailing list
[email protected]
http://lists.software-carpentry.org/listinfo/discuss
