Mastering guide should show 'load.project' step prior to stub.tests()

[mkrasmus]

Report an Issue / Request a Feature

I'm submitting a (Check one with "x") :

• [x] bug report
• [ ] feature request

---

Issue Severity Classification -

(Check one with "x") :

• [ ] 1 - Severe
• [ ] 2 - Moderate
• [x] 3 - Low

Expected Behavior

When following the guide on unit testing the flow of script should include load.project() prior to stub.tests() or will return an error:

> library('ProjectTemplate')
> create.project()
> setwd('new-project')
> stub.tests()
Generating stub tests in tests/autogenerated.R:
Error in get("config", envir = .TargetEnv) : object 'config' not found

Current Behavior

Returns error if steps are followed in order.

Steps to Reproduce Behavior

As above

Possible Solution

include load.project() in the example code/output to the guide

[KentonWhite]

Might be a change to how TestThat runs. I can update the guide and also look at the internals if anything has changed.

[KentonWhite]

ARGH! The error is an image. Added a footnote that some versions of TestThat may require load.project is run before stub.tests