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

Python unit testing #1660

Open
PDoakORNL opened this issue Jun 24, 2019 · 5 comments
Open

Python unit testing #1660

PDoakORNL opened this issue Jun 24, 2019 · 5 comments

Comments

@PDoakORNL
Copy link
Contributor

If we are going to generate important results with python we should consider (must in my opinion) python unit test.
I've used python's built in unittest in the past.

@markdewing
Copy link
Contributor

I prefer the syntax of pytest, but there is a definite advantage to using a built-in facility.

@PDoakORNL
Copy link
Contributor Author

I'll take a look at it. I don't think unittest is optimal its just the one I've used.

@jtkrogel
Copy link
Contributor

N.B. Nexus related tests take a slightly different philosophy. The tests there (see https://github.com/QMCPACK/qmcpack/blob/develop/nexus/bin/nxs-test) are most fairly termed integration tests as they do not contain mock classes, however, once complete, the tests will be called in bottom up dependency order which has a similar effect to unit tests plus mocks. I have no firm opinion about Python tests outside Nexus.

@fdmalone
Copy link
Contributor

fdmalone commented Jul 9, 2019

The afqmctools use unittest. However, they aren't currently running automatically anywhere.

@jtkrogel
Copy link
Contributor

N.B. A subset of Nexus tests can now be run with pytest or nose. This subset is likely to expand in the future, but all tests will remain runnable via nxs-test without reliance on either pytest or nose.

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

No branches or pull requests

4 participants