unittest API for detecting test failure in cleanup/teardown

Open
#68,437 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
testing-qa

Research direction

The issue names unittest cleanup/teardown behavior but provides no files, entry points, or tests. Review the existing unittest cleanup and teardown handling and the linked PR gh-121709 first; the issue does not define the proposed API or a concrete completion test.

Written by the indexing model from the issue text.

Description

easy stdlib type-feature
BPO 24249
Nosy @rbtcollins, @ezio-melotti, @bitdancer, @voidspace, @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 2015-05-20.21:01:55.280>
labels = ['easy', 'type-feature']
title = 'unittest API for detecting test failure in cleanup/teardown'
updated_at = <Date 2020-01-29.03:22:47.048>
user = 'https://github.com/bitdancer'

bugs.python.org fields:

activity = <Date 2020-01-29.03:22:47.048>
actor = 'josephgordon'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2015-05-20.21:01:55.280>
creator = 'r.david.murray'
dependencies = []
files = []
hgrepos = []
issue_num = 24249
keywords = ['easy']
message_count = 5.0
messages = ['243694', '243703', '243704', '243720', '246703']
nosy_count = 6.0
nosy_names = ['rbcollins', 'ezio.melotti', 'r.david.murray', 'michael.foord', 'martin.panter', 'azsorkin']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue24249'
versions = ['Python 3.6']

Linked PRs
  • gh-121709
Dominant language
Python
Stars
77.2k
Forks
36k
Avg merge
1d 9h
Merged PRs (30d)
558

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from python/cpython

All issues in python/cpython

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.