Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some tests were calling
orderly_run
without anenvir
parameter,which ends up running the report in the global environment. This
pollutes that namespace and might affect subsequent tests.
One particular issue I was hitting was a test depending on the global
data
name fromutils
, while other tests were defining a globalvariable with that (unfortunately very common) name.
I've added a
envir = new.env()
parameter to all theorderly_run
calls I could find, and changed the test that depended on
data
to usethe fully qualified name
utils::base
.Running the whole test suite now leaves an unmodified global
environment: