Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2008-October/082982.html below:

[Python-Dev] [Python-checkins] r66863 - python/trunk/Modules/posixmodule.c

• Previous message: [Python-Dev] [Python-checkins] r66863 - python/trunk/Modules/posixmodule.c
• Next message: [Python-Dev] [Python-checkins] r66863 - python/trunk/Modules/posixmodule.c
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

"Martin v. Löwis" writes:

 > I'm skeptical that new tests actually need backporting at all. Python
 > doesn't really get better by new tests being added to an old branch.
 > Near-term, it might get worse because the new tests might cause false
 > positives, making users worried for no reason.

If they do fail, they're not "false" positives.  If they're "false",
then the test is broken, no?  So find a way to label them as tests
added ex-post, with the failures *not* being regressions but rather
latent bugs newly detected, and (presumably) as "wont-fix".

>From a QA point of view one would like to be able to assess how many
latent bugs are making it through to end-of-life.  The new tests will
help in that.

• Previous message: [Python-Dev] [Python-checkins] r66863 - python/trunk/Modules/posixmodule.c
• Next message: [Python-Dev] [Python-checkins] r66863 - python/trunk/Modules/posixmodule.c
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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