-
Notifications
You must be signed in to change notification settings - Fork 21
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
Automated Pint Testing #16
Comments
Awesome; thanks for setting this up! Is it working? I took a peek at your travis.yml file, and on my system at least, I have to change
to
To get the tests to run. |
It seems to work the way it is: But in any case, if I may suggest it, I would be nice to have a better entry point for testing. For example, in Pint we do the following: In the test suite we have function to collect tests and run them. See here This functions is called by a function named In this way users can just run: >>> from pint import test
>>> test() The final piece of the puzzle is a line in
Of course, not all this is necessary. But is nice to have at least a part of it to make it easier for end users to run tests (and for crazy people like me having this kind of integrated testing!). |
As a matter of fact a better entry point for testing has been on my "to-do" list, I just haven't had time to research a better way to set it up. Looks like you've given me the solution I was looking for; thank you! I'll implement this before the next release. |
Provide infrastructure to run all automated tests by calling either python setup.py test or pyEQL.test() Thanks to Hernan Grecco for the suggestion and example code from the pint project. Closes #16.
I have created a repository to make sure we do not break backwards compatibility unintentionally in Pint.
Take a look at https://github.com/hgrecco/pint_downstream_tester
The text was updated successfully, but these errors were encountered: