unittest subTest does not call addFailure
Open
Nobody has claimed this yet.
3.7 (EOL)
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 29152 |
|---|---|
| Nosy | @pitrou, @berkerpeksag, @vadmium |
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 2017-01-04.12:57:35.198>
labels = ['3.7', 'type-bug', 'library']
title = 'unittest subTest does not call addFailure'
updated_at = <Date 2017-01-23.21:12:35.391>
user = 'https://bugs.python.org/kristall'
bugs.python.org fields:
activity = <Date 2017-01-23.21:12:35.391>
actor = 'martin.panter'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2017-01-04.12:57:35.198>
creator = 'kristall'
dependencies = []
files = []
hgrepos = []
issue_num = 29152
keywords = []
message_count = 4.0
messages = ['284635', '284691', '286085', '286117']
nosy_count = 4.0
nosy_names = ['pitrou', 'kristall', 'berker.peksag', 'martin.panter']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'test needed'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue29152'
versions = ['Python 3.5', 'Python 3.6', 'Python 3.7']
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
Start by reading the unittest subTest and addFailure entry points and locate the existing tests for subTest failure handling. Reproduce the reported behavior, then add or update coverage so a failing subTest invokes addFailure as expected and the relevant unittest tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100