Raymond Hettinger writes: > Nobody I know spells setup and teardown as two words. I set up a house of cards. When I'm done, I'm done with setup. Similarly for "tear down" and "teardown". The two word forms are verbs, the one word forms are nouns. I don't think it's worth a column to make that distinction, though. > Another thought is that test suite code is going to get seriously crunched when the new, longer method names meet the 78/80 column > pep 8 restrictions. > > class TestMisc(unittest.test_case): > def lost_four_spaces_here_already(self): Eight spaces, actually. Make that 13 by the time you get to the "." after "self" in the next line. > Are there any ideas for some short, pithy, mnemonic names that are > self-explantory and not full of underscores; something that > wouldn't suck to type hundreds of times in a good test module? "test" or "check" instead of "assert" or "fail_unless" comes to mind to shorten the prefix. But the best I can come up with for "fail_unless_equal" is something like "equalize" which really fails EIBTI.
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