Repository navigation
docs(tests): state corekit, utilities and dumpkit tests' behaviour without change-relative narrative (#1103) - #2202
Conversation
|
Review: NEEDS CHANGES at
There is also one garbled sentence. The rewrites themselves hold against the code, cross-references resolve, the subtest sentence is accurate and the tests pass. The worker is fixing the rest. |
…thout change-relative narrative (#1103) Rewrite comments and docstrings in tests/corekit (except _roundtrip.py), tests/utilities, tests/dumpkit, tests/interface and tests/cli so they state the behaviour pinned and the defect guarded against ("without the fix ...") rather than narrating a change ("now", "used to", "before this change"). Pure history is cut. Prose only: the AST with docstrings stripped is unchanged.
|
Review fixes pushed:
The AST check is clean on all 57 files, and the slice tests pass. A delta review is running. |
2c80e6b to
d0e35e3
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. Test narratives in
tests/corekit/(except_roundtrip.py),tests/utilities/,tests/dumpkit/,tests/interface/andtests/cli/now state the behaviour, not how a change produced it.byteorder.py:33becomes the function name.get(value, default)on an out-of-range value returns the default but logs a CRITICAL error and installs pcapkit's excepthook #1845.subTestis a countedSUBFAILEDentry, while the parent counts as passed.main.