Namespace exports changing upon devtools::test()

[EliMiller]

Running devtools::test() changes the list of exported functions.

> getNamespaceExports("my_package")
[1] "exported_1"  "exported_2" ...
> devtools::test()
Loading my_package
Testing my_package
...
══ Results ══════════════════════════════════════════════════════════════════════════════════════
Duration: 0.4 s

OK:       93
Failed:   1
Warnings: 0
Skipped:  0

Your tests are shining!
... error info below ...
> getNamespaceExports("my_package")
[1] "exported_1" "exported_2" "unexported_1" "unexported_2" ...

Apologies for the lack of a repex, I wasn't sure on how to write one given the problem

[EliMiller]

This has been figured out. From the documentation for testthat::test_dir():

Environments

Each test is run in a clean environment to keep tests as isolated as possible. For package tests, that environment that inherits from the package's namespace environment, so that tests can access internal functions and objects.

[mfherman]

If your question's been answered (even by you!), would you mind choosing a solution? It helps other people see which questions still need help, or find solutions if they have similar problems. Here’s how to do it:

FAQ: How do I mark a solution?

If your question has been answered, don't forget to mark the solution! How do I mark a solution? Find the reply you want to mark as the solution and look for the row of small gray icons at the bottom of that reply. Click the one that looks like a box with a checkmark in it: [image] Hovering over the mark solution button shows the label, "Select if this reply solves the problem". If you don't see the mark solution button, try clicking the three dots button ( ••• ) to expand the full set of options. When a solution is chosen, the icon turns green and the hover label changes to: "Unselect if this reply no longer solves the problem". Success! [solution_reply_author] :information_s…