-
Notifications
You must be signed in to change notification settings - Fork 166
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
Initial support for unit tests of pytest plugins #104
Conversation
One can pass pytest options for unit test run, eg: $ tox -- unittests -v --pdb Which can be helpful during debugging.
There is no reason to have __init__.py in the root directory of the repository.
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.
Hi @mbukatov , even though this is very important, it is a very low priority for now.
We have a huge gap to close in testing OCS so any contribution to test the product itself is with high priority
@RazTamir understood, I will polish it so that it could be merged asap, without adding the tests I originally intended to write. |
That said, the original indentation was valid from PEP8's point of view.
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.
In case you have execution link to ensure this is verified, please add it here
In this case we can consider the output from travis (tox) as verification: https://travis-ci.org/red-hat-storage/ocs-ci/jobs/538111788 |
This pull requests introduces unit tests of our pytest plugins, tested via pytest via pytester, which is official pytest module for testing pytest plugins via pytest.
It contains few simple test cases only, so that it's possible to add unit tests for config and cli option processing later.
Don't squash this pull request into single commit when merging, each commit message is meaningful.