-
Notifications
You must be signed in to change notification settings - Fork 140
[result] fix subtest referencing objects #220
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
[result] fix subtest referencing objects #220
Conversation
385fec7
to
ed4666c
Compare
Codecov Report
@@ Coverage Diff @@
## master #220 +/- ##
==========================================
+ Coverage 94.48% 99.54% +5.05%
==========================================
Files 15 15
Lines 1523 1525 +2
==========================================
+ Hits 1439 1518 +79
+ Misses 84 7 -77
Continue to review full report at Codecov.
|
1 similar comment
Codecov Report
@@ Coverage Diff @@
## master #220 +/- ##
==========================================
+ Coverage 94.48% 99.54% +5.05%
==========================================
Files 15 15
Lines 1523 1525 +2
==========================================
+ Hits 1439 1518 +79
+ Misses 84 7 -77
Continue to review full report at Codecov.
|
Actually it should also fix when there are floats in the subtest |
@dnozay did I do something wrong? |
@XonqNopp - it would be good to have a unit test that demonstrates / exercises the incorrect behavior. |
4488d42
to
e6cf584
Compare
I added tests and tried them: before the fix, the build failed https://travis-ci.org/github/xmlrunner/unittest-xml-reporting/builds/676106789 With the fix it is now passing https://travis-ci.org/github/xmlrunner/unittest-xml-reporting/builds/676107976 However, the pytest step failed. And I must admit that I cannot understand what is wrong after reading the log for 15min. Can you please give me a hint as to what I should fix? |
@dnozay any help to understand how to fix the test would be appreciated ;-) |
I think this is an issue on this seems similar to #189 |
https://github.com/python/cpython/blob/3.8/Lib/unittest/case.py#L375-L407
gonna have to remove the broken test |
remove broken test, see #220 and #189 ``` If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run. ```
@XonqNopp - can you please rebase and try again? I'll merge if CI passes. |
450b461
to
2512b43
Compare
@dnozay all tests passed :-) |
Close #219