-
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
Testing #12
Comments
on second thought, pytest would be a development dependency anyway, as so will flake8 and so be when that is setup |
That would be cool. What do you think we should have tests for? I don't have a strong preference about whether to use such dependencies or not. Either way would work imo. |
everything? haha. |
I mean, sure thing. Unit tests are very nice 😄 We should probably wait for the package logic to move from the main file to init first, though. After that, I'm all for it. |
I am fairly biased to pytest, I find it looks much cleaner. |
Then I see no reason to use anything else. Let's go with PyTest! |
@vivax3794 we should be ready to start writing tests! We're considering changing the way that answers are stored, but that shouldn't change the outputs of using the package in any way. Thanks for helping out. |
Framwork
we could use the built-in unittest to keep with the current no depends, but I really like pytest.
when the tests have been setup they should be used with #8 as well.
I would be more than happy to write the tests
The text was updated successfully, but these errors were encountered: