-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Test Suite Housekeeping (Part 3) #1167
Conversation
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.
Just a minor issue with a bare except that I'd like to avoid, but overall looks really good! Thank you so much!
@fcurella I think travis hanged since the last merge to master. Anyway, looks like I might be rebasing my PR a fair amount prior to getting this merged if I do not split this now, so I will probably wrap this part up soon and continue with a new PR. |
@fcurella I am done for this portion which (I estimate) accounts for 1/3 of the transition. The tests for other providers are a bit tedious/repetitive/lacking, so I am going to think about how to tackle them, and I also do not want to introduce too much |
@malefice It looks great! Impressive work! |
* Add test fixtures exclusive for tests.providers * Pytestify tests.sphinx * Pytestify and improve user agent provider tests * Pytestify barcode provider tests * Fix flake8 bare except issue * Pytestify, reorganize, and improve Generator class tests * Pytestify, reorganize, and improve Faker class tests * Fix test failure * Pytestify currency provider tests * Pytestify isbn provider tests * Pytestify, reorganize, and improve internet provider tests * Pytestify, reorganize, and improve base provider tests * Fix CI errors
Note: I estimate that only 1/3 of the transition is complete.
What does this change
Since
Faker
also now ships its ownpytest
plugin, this PR aims to (fully or partially) transition the test suite from usingunittest
style test topytest
style tests as well as to start usingFaker
's own fixtures in the test suite. This can also serve as a good opportunity to review the quality of individual tests, and improvements will be made whenever possible.