bw2
Give some more help to developers regarding writing new tests
The soon-to-be merged CONTRIBUTING guidelines state that all code changes should have test coverage, either to show that a new feature works or to show up the bug that is being fixed.
It would be helpful to contributors if there were a worked example of how to do this, since the test setup for tests in this module is non-trivial, and contributors may not be familiar with the test framework being used.
Maybe the -- arg separator is a good example? Or maybe not, since this seems to be a bug (or at least an inconsistency) in the underlying argparse module. But I can certainly find something.
Assigning this to myself.
Or rather, I will assign the issue to myself once I have the required level of access to this repo.