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: Add style guide for unit tests
Type: Stage:
Components: Versions:
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: madman bob, steven.daprano, vstinner
Priority: normal Keywords:

Created on 2018-10-31 11:31 by madman bob, last changed 2022-04-11 14:59 by admin.

Messages (3)
msg328986 - (view) Author: Robert Wright (madman bob) * Date: 2018-10-31 11:31
There should be a style guide for tests, to prevent arguments about their use in future code.
msg329008 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2018-10-31 19:35
Context: https://github.com/python/cpython/pull/8548#pullrequestreview-166712031
msg329022 - (view) Author: Steven D'Aprano (steven.daprano) * (Python committer) Date: 2018-10-31 23:10
I think this is being excessively prescriptive and solving a problem that isn't a problem.

But perhaps if you start by proposing a concrete style guide, I can judge better.
History
Date User Action Args
2022-04-11 14:59:07adminsetgithub: 79305
2018-10-31 23:10:00steven.dapranosetnosy: + steven.daprano
messages: + msg329022
2018-10-31 19:35:44vstinnersetnosy: + vstinner
messages: + msg329008
2018-10-31 11:31:54madman bobcreate