R2.4: Add dependency testing to the automation use case about manuscript HOT 2 CLOSED

I do not think we should make this addition. While dependency testing is important for sharing code widely, it falls on the more technical end of the spectrum. We have been encouraged by reviewer 1 in #277 and #278 to reduce jargon and gear our work toward entry-level researchers. Dependency management is out of scope for that group.

from manuscript.

Hi. I agree that both automation and unit dependency testing are more advanced tasks, which many users may not require. Still, it has been more and more encouraged as a way to mitigate errors across research practices. The narrative already incorporated these components when we discussed about validation and verification, but perhaps in a less clear way. Without adding complexity to the narrative, I added a few words to mention that automation can aid the testing of research code and the implementation of workflows for the interpretation, integration and usage of data and software across different sources, and included two citations (one of them being the one that the reviewer provided).

from manuscript.