Skip to content
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

recommended testing protocol #43

Closed
tpapp opened this issue Oct 17, 2017 · 1 comment
Closed

recommended testing protocol #43

tpapp opened this issue Oct 17, 2017 · 1 comment

Comments

@tpapp
Copy link

tpapp commented Oct 17, 2017

The readme cautions that the package

has received little testing in the wild

I would like to help by testing on data I work with, and I am wondering what the recommended testing protocol is. My first-pass approach would be to write, read, and compare, but what's the recommended comparison operator that I should use? iseq from the unit tests?

@JonasIsensee
Copy link
Collaborator

I'd say this counts as outdated.

While the tests can sure use some work, there has been plenty of testing in the wild.

The things to test are whether saving and loading does not throw and
whether loaded results equal what was writtenj

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants