unittest.mock spec and create_autospec should support type-hints
還沒有人認領這個 Issue。
- 主要語言
- Python
- 星號
- 77.2k
- 分支
- 36k
- PR 合併指標
- PR 指標待擷取
描述
Feature or enhancement
Proposal:
Current recommendation for spec=... and create_autospec is to set a default class value in case of attributes created within an instance's __init__():
Probably the best way of solving the problem is to add class attributes as default values for instance members initialised in
__init__()
The problem is that like written, Nones are never useful and together with spec_set=True it just results in a regular mock that accepts everything.
That recommendation and method are unfortunately very old and they existed long before the type hinting system was so developed. I believe type hints can now be reliably used to infer the spec, at least in simple terms, and in the other cases the same behavior as None can be implemented.
from unittest.mock import create_autospec
class A:
a: dict[str, int]
b: Iterator[str]
c: int | str | complex
mock = create_autospec(A)
mock().a # should be supported, with a dict spec.
mock().b # Iterator spec
mock().c # Too complex... Any spec (just like current behavior for None)
It will lead into more accurate unit tests, and we can optionally hide the behavior behind a boolean such as infer_types=True.
Has this already been discussed elsewhere?
This is a minor feature, which does not need previous discussion elsewhere
Links to previous discussion of this feature:
No response
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
首先追蹤 unittest.mock 和 create_autospec 的進入點,包括 spec_set=True 目前如何處理在 init 中初始化的執行個體屬性。定義簡單型別提示、複雜聯集和提議的選用推論旗標的行為;完成標準是要求的註解能產生適當的 spec,同時不變更不支援情況的回退行為。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- python
- 領域
- testing-qa
- Issue 類型
- 功能
- 難度
- 5/5
- 預估耗時
- 一週以上
- 活躍度
- 停滯
- 描述清晰度
- 基本清楚
- 新手友好度
- 35/100