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
Change parameterized testing system to be compatible with unittest #712
Conversation
Summary: The previous implementation of parameterized testing worked by modifying test.common_utils inplace. This doesn't work in general because unittest's contract with test modules is such that it must be able to load the module and run the test itself. Because the previous implementation needed to load the module and modify it, it is incompatible. Reviewed By: mthrok Differential Revision: D21964676
Codecov Report
@@ Coverage Diff @@
## master #712 +/- ##
=======================================
Coverage 89.23% 89.23%
=======================================
Files 26 26
Lines 2350 2350
=======================================
Hits 2097 2097
Misses 253 253 Continue to review full report at Codecov.
|
Can you give a snippet of the error we were getting on the internal side? |
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.
Based on offline discussion, this LGTM. I agree modules should not be modified by other modules.
Are there other cases behaving like this that use |
Ya, I am working to remove them now. |
Thanks |
Signed-off-by: nbqu <dk41245@gmail.com>
Summary: The previous implementation of parameterized testing worked by modifying test.common_utils inplace. This doesn't work in general because unittest's contract with test modules is such that it must be able to load the module and run the test itself. Because the previous implementation needed to load the module and modify it, it is incompatible.
Reviewed By: mthrok
Differential Revision: D21964676