-
Notifications
You must be signed in to change notification settings - Fork 0
Write unit tests #18
Copy link
Copy link
Open
Labels
enhancementNew feature or requestNew feature or requestoptionalOnly a nice-to-have feature, can be skipped (especially if it conflicts with a non-optional issue)Only a nice-to-have feature, can be skipped (especially if it conflicts with a non-optional issue)robotIssue surfaced from automated review processesIssue surfaced from automated review processes
Description
Activity
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or requestoptionalOnly a nice-to-have feature, can be skipped (especially if it conflicts with a non-optional issue)Only a nice-to-have feature, can be skipped (especially if it conflicts with a non-optional issue)robotIssue surfaced from automated review processesIssue surfaced from automated review processes
Consider writing some unit tests (perhaps in a separate
tests.py?) to establish that functions with clear input -> output expectations work to specification. Most functions probably don't need tests, but things involving math or string processing might (e.g. checking that Mac/Linux style paths and Windows style paths run the same for all path-based functions).