[issue13394] Patch to increase aifc lib test coverage

Ezio Melotti report at bugs.python.org
Tue Dec 13 15:11:11 CET 2011


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

Thanks for splitting the patch.
I tried to apply the patch to 3.2 and I have 3 comments:
1) you changed a commented-out assertEqual with an assertNotEqual, because "ULAW is lossy compression, so frames *may* not match".  Does it mean that sometimes they might match and make the test fail or that they are always different for this specific test?  In the first case the test should make sure to have a consistent result and avoid sporadic failures.  In the second case the check could be removed altogether, because producing different results is not a feature of the format, but just a detail that depends on the input.
2) when I run the tests I now get 3 warnings:
Warning: bad COMM chunk size
Warning: bad COMM chunk size
Warning: MARK chunk contains only 0 markers instead of 1
These should be silenced, or better, tested with self.assertWarns (assertWarns should silence them too).
3) there's some trailing space just before test_write_header_comptype_raises.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue13394>
_______________________________________


More information about the Python-bugs-list mailing list