-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regression tests and (actual) unit tests #48
Comments
craffel
added a commit
that referenced
this issue
Apr 23, 2014
…corated by score #45 also using nose to allow for loops while still reporting args
craffel
added a commit
that referenced
this issue
Apr 23, 2014
craffel
added a commit
that referenced
this issue
Apr 24, 2014
craffel
added a commit
that referenced
this issue
Apr 24, 2014
…t nosetests' verbose output is clearer, to be closer to onset or beat's tests
craffel
added a commit
that referenced
this issue
Apr 24, 2014
craffel
added a commit
that referenced
this issue
Apr 25, 2014
Melody has unit tests but the to_cent_voicing unit test is just a placeholder right now. |
Punting |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Each task submodule should have a testing script in
tests
which performs unit/sanity tests and regression tests against the current stable implementation of the code. This is all primarily to prevent bugs from creeping in the code. We're not trying to unit test against an existing implementation anymore.Regression tests
Unit tests
The text was updated successfully, but these errors were encountered: