-
Notifications
You must be signed in to change notification settings - Fork 6
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
Tests #4
Comments
Yeah, that sounds like a good idea :) When do you think is a good time to start testing? Since the module is still under development, lots could change, even something like the arguments to the methods. |
I think now is a good time. If only to document and assert for ourselves things like #3 and flesh out all other edge cases and obscurities that we find as we develop. Ideally we'd submit PRs with just tests, and work out the implementation from there. |
How come we need both AppVeyor and Travis for tests? |
AppVeyor does Windows, Travis does Unix |
Ahh :) What about the testing framework? You have more experience with them than I, but seems like nose2 might be a good choice? |
Up to you :) I tend to go with nose, but it's a personal choice. I've heard good things about py.test too. |
The testing framework ended up being pytest :) |
Let's get AppVeyor and Travis into the game, with tests for Windows and Unix.
The text was updated successfully, but these errors were encountered: