-
Notifications
You must be signed in to change notification settings - Fork 2
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 #35
Conversation
@jhnnsnk ; this can be merged. Shouldn't break anything; but the github action will complain a bit if pushed code doesn't conform to flake8 standards (less stringent than the other PEP8 PR). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. Just one minor thing so far and a question. :-)
|
||
""" | ||
|
||
import unittest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We recently used pytest
in a different project (https://github.com/INM-6/lif_meanfield_tools) and I really liked it. Are there any specific reasons for using unittest
here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
None other than that unittest
is part of the standard library and pytest
is not. But I install it anyway to run the tests so please go ahead and use the latter if you want in the future.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think unittest
is ok here. I will merge.
Co-authored-by: Johanna Senk <[email protected]>
This should get #16 started by running test suite in /mesocircuit/tests/ automatically as well as some flake8 linting (#9).