Wishlist for improving testing/demoing

[maelle]

• more use of a local remote.
• also use this local remote in a demo in an article.
• mock the CRAN release somehow, for testing and also for demoing.
• there's a tension between testing and debugging tests regarding the use of local_ functions in tests: changing the local directory makes it hard, well clumsy, to run tests interactively.
• how to make init_release() quiet in tests #702
• Remove all snapshot_variant("testthat")? #695
• Sandbox companion project #8

@krlmlr

[maelle]

Notes on pre_release() testing

For create_pull_request(), use test switch or mocking.
use rlang interactive option to circumvent edit_file()

[krlmlr]

Let's start with a simple R script that goes through the entire release process. It should work offline, for speed, mocking away anything that might need connectivity.

[krlmlr]

Seems good enough now?

[maelle]

yes but we don't have "mock the CRAN release somehow, for testing and also for demoing." in particular

[krlmlr]

We're mocking it away, we can call release() in the tests without failing. What else do we need to do?

[maelle]

right, we're avoiding more than mocking, but i guess mocking wouldn't bring much