Repository navigation
docs(tests): state project tests' behaviour without change-relative narrative (#1103) - #2203
Conversation
|
Review: NEEDS CHANGES at |
…arrative (#1103) Rewrite comments and docstrings in tests/project that describe a fix relative to the change ("now", "no longer", "used to", "before #NNN", "the old X") as timeless statements of the behaviour pinned or the defect guarded against; cut history that only reads as history. Prose only: every changed module's AST is identical once docstrings are stripped.
|
Review fixes pushed:
The AST check is clean, and the touched files pass their tests. A delta review is running. |
9ac0086 to
9463a15
Compare
|
Review: GOOD TO GO at |
|
Ready to merge at
|
|
Coverage: 91.55% (unit tier, Python 3.15,
Per-file detail: the |
make testpasses, and a test case covers the changeWhat is the purpose of your pull request?
docs— documentation onlyDescription
Part of #1103, ruling 1: the narratives in
tests/project/say what the code does now, not how a change got it there. #2199 ownstest_python_versions_1660.pyandtest_resource_monitor_1740.py, so this PR leaves them out.test_isort_cleandocstring's three-fix story, which becomes three bullets on why the Makefile lines are shaped as they are.test_conda_no_windows_steps_1967said the conda jobs have no Windows leg. Both have had one since Conda: bring back the Windows (win-64) package, in two phases #2060.subTestlabels, which are code.main's AST.