Mock.assert_has_calls works strange
Open
Nobody has claimed this yet.
3.10
3.8 (EOL)
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 43371 |
|---|---|
| Nosy | @cjw296, @voidspace, @lisroach, @corona10, @mariocj89, @tirkarthi, @kamilturek |
| Files |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = None
created_at = <Date 2021-03-02.14:31:34.302>
labels = ['3.8', 'type-bug', 'library', '3.10']
title = 'Mock.assert_has_calls works strange'
updated_at = <Date 2022-01-16.03:21:02.855>
user = 'https://bugs.python.org/dmitriymironiyk'
bugs.python.org fields:
activity = <Date 2022-01-16.03:21:02.855>
actor = 'roysmith'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2021-03-02.14:31:34.302>
creator = 'dmitriy.mironiyk'
dependencies = []
files = ['49845']
hgrepos = []
issue_num = 43371
keywords = []
message_count = 4.0
messages = ['387932', '388758', '397172', '410667']
nosy_count = 10.0
nosy_names = ['roysmith', 'cjw296', 'michael.foord', 'lisroach', 'corona10', 'mariocj89', 'xtreak', 'dmitriy.mironiyk', 'kamilturek', 'mardoxx']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue43371'
versions = ['Python 3.8', 'Python 3.10']
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names test_mock_asser_has_calls.py as its only file; begin by reading it and reproducing the reported Mock.assert_has_calls behavior. Clarify the expected result from the issue discussion before changing code, then add a focused regression test and run the relevant mock tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100