Closed hrszpuk closed 1 year ago
Due to a lack of activity, this issue has been deemed stale. If this level of activity continues for a further 5 days this issues will be closed.
This issue has been closed due to a lack of activity!
Due to a lack of activity, this issue has been deemed stale. If this level of activity continues for a further 5 days this issues will be closed.
This issue has been closed due to a lack of activity!
Is your feature request related to a problem? Please describe. Frequently having to test commands/subcommands and debug issues. If there is an issue with commands/subcommands/flags then I have to manually go into the code and check what is and is not working. This is quite inefficient and it would be better to have unit tests that can not only test specific commands, but also test specific functions. Now, this would be a major time sink because unit tests for each function is a lot of extra code. However, I think it would be more efficient in the long term, not to mention a lot easier to find where issues in code are coming from. With testing added there could also be a GitHub workflow added run tests before a pull request can be merged into master. This would guarantee master is always functional.
Describe the solution you'd like
go test
) for pull requests.Describe alternatives you've considered Testing manually is the current solution but is inefficient.