This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: run the testsuite in batched mode
Type: enhancement Stage: patch review
Components: Tests Versions: Python 3.5
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: doko
Priority: normal Keywords: patch

Created on 2013-04-17 19:38 by doko, last changed 2022-04-11 14:57 by admin.

Files
File name Uploaded Description Edit
batch-test.diff doko, 2013-04-17 19:37
Messages (2)
msg187199 - (view) Author: Matthias Klose (doko) * (Python committer) Date: 2013-04-17 19:37
running all the tests in one batch sometimes can go wrong. there is of course the --single mode, but starting the testsuite for each single test seems to be a bit of overhead.  So extend the --single API to something like --next=<n> which runs the next <n> tests. or would --batch be a better name? and maybe don't change the single default parameter in the signature, and introduce a new parameter.

the proposed patch is currently against the 3.3 branch, and without doc changes.
msg223130 - (view) Author: Mark Lawrence (BreamoreBoy) * Date: 2014-07-15 17:58
I'm assuming that this classifies as an enhancement and that the whole world ought to be interested in regrtest.
History
Date User Action Args
2022-04-11 14:57:44adminsetgithub: 61983
2019-04-26 19:40:23BreamoreBoysetnosy: - BreamoreBoy
2014-07-15 17:58:38BreamoreBoysetversions: + Python 3.5, - Python 3.4
nosy: + BreamoreBoy

messages: + msg223130

type: enhancement
2013-04-17 19:38:00dokocreate