[Python-Dev] Test the test suite? (original) (raw)
Xavier de Gaye xdegaye at gmail.com
Wed Aug 28 16:13:41 CEST 2013
- Previous message: [Python-Dev] Test the test suite?
- Next message: [Python-Dev] Test the test suite?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
It happens that few tests are also never run because of name conflicts. See issue 16056.
Xavier
On Wed, Aug 28, 2013 at 1:37 PM, Victor Stinner <victor.stinner at gmail.com> wrote:
Hi,
I just noticed that tests using @requiresfreebsdversion and @requireslinuxversion decorator from test.support are never run since this commit (almost 2 years ago): changeset: 72618:3b1859f80e6d user: Charles-François Natali <neologix at free.fr> date: Mon Oct 03 19:40:37 2011 +0200 files: Lib/test/support.py description: Introduce support.requiresfreebsdversion decorator. ... raise unittest.SkipTest( - "Linux kernel %s or higher required, not %s" - % (minversiontxt, versiontxt)) - return func(*args, **kw) - wrapper.minversion = minversion + "%s version %s or higher required, not %s" + % (sysname, minversiontxt, versiontxt))
I don't want to blame Charles-François, nobody saw the issue during 2 years! No, my question is: how can we detect that a test is never run? Do we need test covertage on the test suite? Or inject faults in the code to test the test suite? Any other idea? I fixed the decorators in Python 3.3 (84debb4abd50) and 3.4 (f98fd5712b0e). Victor
Python-Dev mailing list Python-Dev at python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/xdegaye%40gmail.com
-- Xavier
Les Chemins de Lokoti: http://lokoti.alwaysdata.net
- Previous message: [Python-Dev] Test the test suite?
- Next message: [Python-Dev] Test the test suite?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]