This approach actually includes 3 types of tests:

1. fast tests with testthat which run regularly
2. fast tests that are CRAN-like which run on changes (and change requests to) the default branch
3. slow tests that track memory usage

The first two are implemented (about to be - see furrer-lab/devel-abn#100 ), what remains is the tests that include the tracking of memory usage.

Originally posted by @j-i-l in #81

We want to run tests with valgrind enabled (what else?) if we have a release candidate.

Depending on what it is exactly that we want to track it might be enough to run R CMD check with --use-valgrind, in which case we could handle this by setting some variables in the existing github action CRAN_checks.

1. We should decide what sort of memory check we want to run
2. Implement the action accordingly