Add public TestCase method/property to get result of current test
Open
Nobody has claimed this yet.
3.9 (EOL)
stdlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 32926 |
|---|---|
| Nosy | @rbtcollins, @ezio-melotti, @voidspace |
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 2018-02-23.22:08:37.011>
labels = ['type-feature', 'library', '3.9']
title = 'Add public TestCase method/property to get result of current test'
updated_at = <Date 2019-06-27.09:20:46.412>
user = 'https://bugs.python.org/VictorEngmark'
bugs.python.org fields:
activity = <Date 2019-06-27.09:20:46.412>
actor = 'jdemeyer'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2018-02-23.22:08:37.011>
creator = 'Victor Engmark'
dependencies = []
files = []
hgrepos = []
issue_num = 32926
keywords = ['patch']
message_count = 1.0
messages = ['312671']
nosy_count = 4.0
nosy_names = ['rbcollins', 'ezio.melotti', 'michael.foord', 'Victor Engmark']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue32926'
versions = ['Python 3.9']
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 reviewing the public TestCase API and the linked issue discussion to determine what “result of current test” should mean and whether it belongs as a method or property. Done means the proposed public interface and its behavior are clearly defined, implemented in the library, and covered by tests; no file or test path is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100