Right now there are just a couple of actual tests in the test/ folder, and they leave huge portions of the code untouched.
Eventually, we will need a suite of unit tests and comprehensive integration tests that reasonably convince us that a new change won't break anything. We'll also want to integrate with CircleCI and github so that we can evaluate pull requests from the web (but that will come later).
I'll try to update this issue with our progress as time goes on, but a good start would be unit tests for:
- each hyperpartition for each classification method
- each
database.py create/query/update function
- hyperpartition enumeration
- hyperpartition selection/parameter tuning
- metric computation in
metrics.py
- data loading and encoding with a variety of quirky data types
- serialization/deserialization of models/metrics objects
Right now there are just a couple of actual tests in the
test/folder, and they leave huge portions of the code untouched.Eventually, we will need a suite of unit tests and comprehensive integration tests that reasonably convince us that a new change won't break anything. We'll also want to integrate with CircleCI and github so that we can evaluate pull requests from the web (but that will come later).
I'll try to update this issue with our progress as time goes on, but a good start would be unit tests for:
database.pycreate/query/update functionmetrics.py