> Note that you might want to break it up into subtests; for example, > test_fork.py tests os.fork() already. So you could have one test case > for file-related operations, another for uid-related, etc. A full > test_os.py would be huge and ungainly. +1. If the tests would also do the import in the right way, i.e. test_os_symlink would do a "from os import symlink", then on each platform it would only try the tests that are relevant to the platform, while the others would be skipped with an "optional feature couldn't be imported", in stead of crashing the whole test_os. -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen@oratrix.com | ++++ if you agree copy these lines to your sig ++++ www.oratrix.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm
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