This PR makes all the changes necessary for the unit tests to work on Windows. Mostly this is changes in the test suite itself, but there are some changes in the actual code. This doesn't guarantee full functionality--I haven't run the functional, a lot of the scripts aren't tested, etc. But it's an incremental step. #116 would probably be the next step.
With this PR, all the unit tests also run on Mac. I didn't make any changes to make that happen, but I only tested on Mac once all the Windows fixes were in.
PR Checklist
[X] Pull request has descriptive title
[X] Pull request gives overview of changes
[X] New code has inline comments where necessary
[X] (N/A) Any new modules, functions or classes have docstrings consistent with dbprocessing style
[X] (N/A) Major new functionality has appropriate Sphinx documentation
[X] (N/A) Added an entry to release notes if fixing a major bug or providing a major new feature
[X] New features and bug fixes should have unit tests
[X] Relevant issues are linked in the description (use Closes # if this PR closes the issue, or some other reference, such as See # if it is related in some other way)
This PR makes all the changes necessary for the unit tests to work on Windows. Mostly this is changes in the test suite itself, but there are some changes in the actual code. This doesn't guarantee full functionality--I haven't run the functional, a lot of the scripts aren't tested, etc. But it's an incremental step. #116 would probably be the next step.
With this PR, all the unit tests also run on Mac. I didn't make any changes to make that happen, but I only tested on Mac once all the Windows fixes were in.
PR Checklist
Closes #if this PR closes the issue, or some other reference, such asSee #if it is related in some other way)