You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of the JOSS review, unit tests are required to demonstrate the functionality of the code:
Automated tests: Are there automated tests or manual steps described so that the functionality of the software can be verified?
While automated tests are not required, I would highly suggest implementing them using github actions as it will help with the long-term maintainability of the code. Similarly, I would recommend setting up a linter (but that's optional of course).
I see that there is something implemented in tests/, but it includes hard-coded paths, which are specific to the maintainer's system. These fail when I run it on my computer.
The text was updated successfully, but these errors were encountered:
As part of the JOSS review, unit tests are required to demonstrate the functionality of the code:
While automated tests are not required, I would highly suggest implementing them using github actions as it will help with the long-term maintainability of the code. Similarly, I would recommend setting up a linter (but that's optional of course).
I see that there is something implemented in
tests/
, but it includes hard-coded paths, which are specific to the maintainer's system. These fail when I run it on my computer.The text was updated successfully, but these errors were encountered: