Patch to Increase test coverage of unittest.runner.TextTestResult
Open
Nobody has claimed this yet.
tests
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 27395 |
|---|---|
| Nosy | @berkerpeksag |
| 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 2016-06-27.01:32:11.208>
labels = ['type-feature', 'tests']
title = 'Patch to Increase test coverage of unittest.runner.TextTestResult'
updated_at = <Date 2016-08-17.03:03:16.254>
user = 'https://bugs.python.org/PamMcANulty'
bugs.python.org fields:
activity = <Date 2016-08-17.03:03:16.254>
actor = 'berker.peksag'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Tests']
creation = <Date 2016-06-27.01:32:11.208>
creator = 'Pam.McANulty'
dependencies = []
files = ['43551']
hgrepos = []
issue_num = 27395
keywords = ['patch']
message_count = 1.0
messages = ['269330']
nosy_count = 2.0
nosy_names = ['berker.peksag', 'Pam.McANulty']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue27395'
versions = ['Python 3.5', 'Python 3.6']
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 linked textresult_coverage.patch and inspecting unittest.runner.TextTestResult. Run the relevant unittest tests and use the patch to identify the intended coverage additions; done means the proposed cases are included and the tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100