10 Oct
2008
10 Oct
'08
1:22 a.m.
"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.