On 01/05/2019 07:46, Serhiy Storchaka wrote: > 01.05.19 00:24, Chris Withers пише: >> I have a crazy idea of getting unittest.mock up to 100% code coverage. >> >> I noticed at the bottom of all of the test files in testmock/, there's a: >> >> if __name__ == '__main__': >> unittest.main() >> >> ...block. >> >> How would people feel about these going away? I don't *think* they're >> needed now that we have unittest discover, but thought I'd ask. > > These lines were added for purpose. They are needed for running tests in > separate file as a script. > > $ ./python Lib/unittest/test/testmock/testcallable.py -v > test_attributes (__main__.TestCallable) ... ok > test_create_autospec (__main__.TestCallable) ... ok > test_create_autospec_instance (__main__.TestCallable) ... ok > test_hierarchy (__main__.TestCallable) ... ok > test_non_callable (__main__.TestCallable) ... ok > test_patch_spec (__main__.TestCallable) ... ok > test_patch_spec_callable_class (__main__.TestCallable) ... ok > test_patch_spec_instance (__main__.TestCallable) ... ok > test_patch_spec_set (__main__.TestCallable) ... ok > test_patch_spec_set_instance (__main__.TestCallable) ... ok > test_subclasses (__main__.TestCallable) ... ok Right, but that's not the documented way of running individual suites in the devguide. I'm happy to remove these on the basis that there should be one and only one way of doing things like this. Chris
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4